Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!ficc!ihsan From: ihsan@ficc.ferranti.com (jaleel ihsan) Newsgroups: comp.protocols.tcp-ip Subject: Re: timimg-out a socket read Message-ID: Date: 29 Jun 90 21:35:39 GMT References: <12600781585.32.LYNCH@A.ISI.EDU> Organization: Ferranti International Controls Corporation Lines: 16 In article <12600781585.32.LYNCH@A.ISI.EDU>, LYNCH@A.ISI.EDU (Dan Lynch) writes: > 1) As noted by Comer, the application (meaning vendor) is not obliged > to expose the timer values to the application, but also, the vendor is certainly > not prevented from doing so. Most implementations are, in fact, not too > good about letting the individual application instance set values such > as timer values. This is simply a matter of choice. The protocol supports > the concept, but if an implementaiton had to keep track of this on a > "per instance" basis, it would add to the implementation storage space > requirements. I agree asking TCP to keep timers on a "per instance" basis would be an unreasonable and I dont want to be unreasonable !!! However asking the OS to keep a timer on a "per read" basis would not be an unreasonable request. Jaleel