W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2005

[whatwg] web-apps - TCPConnection

From: Henri Sivonen <hsivonen@iki.fi>
Date: Sun, 6 Nov 2005 12:39:29 +0200
Message-ID: <B9C7738B-25BE-46E5-ABA2-564E20156E19@iki.fi>
On Oct 18, 2005, at 06:14, S. Mike Dierken wrote:

> Okay. Outbound messages are obviously not a problem. Accepting  
> unsolicited
> inbound messages isn't feasible (& the unsolicited part is an  
> invitation to
> spam). Having the client initiate the connection & then receiving/ 
> responding
> to inbound requests is what it sounds like you would need.
> If the browser had an HTTP daemon built-in, would that work?

A HTTP daemon in the browser is not strictly required.

Rumor (which I have not verified) has it that there are successful IP  
over HTTP implementations for the purpose of circumventing strict  
corporate firewalls. An HTTP client behind the firewall issues  
requests to an accomplice HTTP server outside the firewall which  
routes the IP packets to and from the Internet. Outbound packets are  
POSTed to the server. The server sends inbound packets in the  
response stream of the most recent POST. The responses are closed on  
the server only upon seeing the next POST request.

Henri Sivonen
hsivonen at iki.fi
Received on Sunday, 6 November 2005 02:39:29 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:43 UTC