How to achieve application reliability

James Smith jsmith at
Sun Dec 5 07:05:21 UTC 1999

You got it! It's those darn application programmers! :-)  Realistically it
would make sense for browsers to try alternate DNS info, but I guess
there's no crying over spilt milk.

James Smith, CCNA
Network/System Administrator

2140 Winston Park Drive, Suite 203
Oakville, ON, CA L6H 5V5         
Tel:   905-829-3389 (email preferred)
Fax:  905-829-5692
1-877-DXSTORM (1-877-397-8676)

On 4 Dec 1999, Sean Donelan wrote:

> On Sat, 04 December 1999, James Smith wrote:
> > internetsecure to type in the credit card.  The problem with Round-Robin
> > DNS is the possibility of the consumer's web browser picking up an IP
> > address of a server that is down.  If it was a real payment gateway, your
> Finally, a problem I can agree with.  Netscape's browser did some interesting
> things for application reliability when accessing  But for
> other web sites it seems to be one strike and you're out.  Other browsers
> followed their lead.  Actually, I think Mosiac was first, so the programmer
> meme was already formed.  The original CERN web browser did try alternate A
> records.  The CERN browser had a problem handling interrupts when the user
> got tired of waiting, so the Mosaic "error-recovery" method of the user
> clicking on refresh until it finally worked seemed like an improvement.
> The law of unintended consequences?
> The application programmers will say its the networks fault.  The network
> engineers will say its the applications fault.  And the user says a pox
> on all your houses.

More information about the NANOG mailing list