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?
Best,
Nathan
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
