- From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
- Date: Thu, 19 Jun 2008 13:07:53 +0200
Correct me if I am wrong: no two-way TCP daemon like telnet, ssh, POP3, NNTP or IMAP allows reconnecting to an existing session when the connection drops and for UDP daemons this question is moot because the connection never drops although it can occasionally fail. Why should a custom connection from inside the browser make an exception? Chris -----Original Message----- From: whatwg-bounces@lists.whatwg.org [mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Frode Borli Sent: Thursday, June 19, 2008 12:53 AM To: whatwg at whatwg.org Subject: [whatwg] Suggestion of an alternative TCPConnection implementation I see one problem, and that is if the connection is lost (for example because of a proxy server): This could be fixed creating a new header ment for storing a client session id. If we standardize on that, the web server could automatically map the client back to the correct instance of the server application and neither the client, nor the server application need to know that the connection was lost. Any feedback will be appreciated.
Received on Thursday, 19 June 2008 04:07:53 UTC