On Wed, 2003-09-24 at 21:18, David Roden wrote: > Niklas Bergh wrote: > > > Idle connections will be dropped in favor of new incoming connections > > as soon as there are any of those.... > > Isn't an idle connection killed by the IP stack after some time anyhow?
(Of course, IP doesn't specify sessions: they arise in higher level protocols like TCP). I've seen an XTerm unplugged while logged in. The X Client programs continued to run until the XTerm was turned back on. Then immediately they were closed. (There might be some timers running at the X protocol level, so maybe I turned the XTerm back on before those expired). Or disconnect the network segment of a workstation, then shut it down. It's TCP sessions stay open until you both reboot it and reconnect the segment. If you shut it down with the segment up, the connections get closed when the tasks are killed. I've watched idle connections on freenet: every 2 or 4 minutes, a TCP packet comes through with the same ACK as before, sending zero bytes and specifying a window size. And I believe if a peer becomes disconnected without the chance to close TCP connections, they stay open until the peer reconnects to the network and it's TCP stack sends reset packets. It it got a different IP number, the connections stay open until someone else starts a TCP stack using that IP number. Hmm, ... what does freenet do if a peer connects from a new IP number while connections are still open to it on the old IP? > -- > Edward J. Huff <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
