[whatwg] WebSocket support in HTML5

[Kristof Zelechovski]

If you are in control of the server, you can simulate datagram sockets with
one-shot controlled sockets and multicast socket with a central dispatcher
that all interested parties can register with.  For access to external
services that already accept datagram packets only, a gateway of some sort
may be necessary indeed.  Services that respond to multicast packets are
never external so it is not an issue, except for an internal burglar.
And I wonder what comes next.  Would you like to trace route from
JavaScript?  Or perhaps some ARP poisoning stuff, or a packet sniffer?  Come
on.
Chris

-----Original Message-----
From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Richard's Hotmail
Sent: Saturday, September 27, 2008 3:49 AM
To: ddailey; whatwg at whatwg.org
Subject: Re: [whatwg] WebSocket support in HTML5

I am just asking why Sockets are being re-invented for html5, and  in such a
restricted and watered-down fashion. If you guys/gals really like to build
an integer 7 bits at a time or "frame" UTF-8 then more power to you; just
please stop forcing every one else to perfoem the same contortions. Please
gives us a normal a Socket (UDP and Multicast too please) Subject it to
same-origin policy or whatever else is reqd.