W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

Re: Embedding WebSocket Servers in Web Pages

From: Nathan <nathan@webr3.org>
Date: Tue, 30 Nov 2010 17:14:57 +0000
Message-ID: <4CF53111.70300@webr3.org>
To: Toni Ruottu <toni.ruottu@iki.fi>
CC: public-webapps@w3.org, Konrad Markus <konrad.markus@hiit.fi>, Sasu A O Tarkoma <starkoma@cc.helsinki.fi>
Hi Toni,

Any notes or thoughts on the DNS and IP Routing side of things, as in 
how to distinguish between the various listening browsers on my private 
network which all share a single public IP address, and also how to 
negate conflicts + expose the details of the listening socket to the 
user in order to make a connection over the web.

As in, what address do I provide you with (and how do I find it) so that 
we can use the chat demo client-to-client, also how to communicate that 
address when the connection hasn't been made? out-of-band via some other 
messaging system?



Toni Ruottu wrote:
> Hello,
> I work for the computer science department at the University of
> Helsinki, Finland. We've been trying to define an API that would allow
> web site developers to run simple servers in their web pages. The
> motivation behind the research is establishing some ground for
> browser-to-browser networking, enabling web sites to co-operate with
> end-user systems in new ways.
> Today, we are publishing our API draft and working prototype at
> http://browsersocket.org/ We are hoping our work will be useful for
> people designing related web standards. We look forward to discussing
> related topics on the mailing lists.
>   --Toni
Received on Tuesday, 30 November 2010 17:15:54 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:28 UTC