Re: Wow
> HTTP (as I implemented it) does not timeout - it waits for the OS to
> declare the socket dead. I should add a timeout, but I'm not sure what a
> good value would be...
How about "no data received for 60 seconds"? Part of it depends on how the
error is dealt with, too. If after a timeout it simply makes a new connection
with a new range, that should be fine (only if the server supports Range:
though).
Brian
( bcwhite@verisim.com )
-------------------------------------------------------------------------------
Seize the moment! Live now. Make "now" always the most important time. -- JLP
--
To UNSUBSCRIBE, email to deity-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to:
- References:
- Re: Wow
- From: Jason Gunthorpe <jgg@gpu.srv.ualberta.ca>