On 1/7/2004 10:59 AM, Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu wrote:
On Wed, 07 Jan 2004 10:05:11 CST, "Eric A. Hall" said:
The client could simply be waiting on some other event or input, like
a password for AUTH, and not borked or dead.
A case could be made that if you've been sitting at a password prompt
for THAT long, the liveware has probably popped out to Applebee's for
lunch and the connection is *effectively* borked.
...so they should be made to feel the wrath of valdis, and telling them
that the session has timed out would ease some of their discomfort, and we
can't have that now can we :)
Where do you draw the line?
the 'line' is what the design principles say, which is that application
errors should be reported in the application stream.
--
Eric A. Hall http://www.ehsco.com/
Internet Core Protocols http://www.oreilly.com/catalog/coreprot/