Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!ASYLUM.SF.CA.US!romkey
From: romkey@ASYLUM.SF.CA.US (John Romkey)
Newsgroups: comp.protocols.tcp-ip
Subject: Monitoring TCP/IP sockets
Message-ID: <9101291251.AA12293@asylum.sf.ca.us>
Date: 29 Jan 91 20:51:55 GMT
References: <9101291553.AA06606@litwin.jpl.nasa.gov.>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 10

You can't always tell within a second or two whether the physical
connection between two systems is broken. Sometimes the break is a
router crashing. Sometimes it's an AT&T fiberoptic cable cut by a
backhoe in upstate New York when you're in Dallas and the computer
you're talking to is in San Francisco. Most applications want to be
tolerant of order-of-several-minutes disruption of communications,
because there are too many real world transient conditions that aren't
readily distinguishable from long term failures.
		- john romkey			Epilogue Technology
USENET/UUCP/Internet:  romkey@asylum.sf.ca.us	FAX: 415 594-1141