016329.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [whatwg] WebSocket support in HTML5
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20support%20in%20HTML5&In-Reply-To=%3CD8C021EF5AE346CB9BF2851E8A77B3F3%40POCZTOWIEC%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="016318.html">
   <LINK REL="Next"  HREF="016351.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[whatwg] WebSocket support in HTML5</H1>
<!--htdig_noindex-->
    <B>Kristof Zelechovski</B> 
    <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20support%20in%20HTML5&In-Reply-To=%3CD8C021EF5AE346CB9BF2851E8A77B3F3%40POCZTOWIEC%3E"
       TITLE="[whatwg] WebSocket support in HTML5">giecrilj at stegny.2a.pl
       </A><BR>
    <I>Sat Sep 27 03:58:29 PDT 2008</I>
    <P><UL>
        <LI>Previous message: <A HREF="016318.html">[whatwg] WebSocket support in HTML5
</A></li>
        <LI>Next message: <A HREF="016351.html">[whatwg] WebSocket support in HTML5
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16329">[ date ]</a>
              <a href="thread.html#16329">[ thread ]</a>
              <a href="subject.html#16329">[ subject ]</a>
              <a href="author.html#16329">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--/htdig_noindex-->
<!--beginarticle-->
<PRE>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: <A HREF="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">whatwg-bounces at lists.whatwg.org</A>
[mailto:<A HREF="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">whatwg-bounces at lists.whatwg.org</A>] On Behalf Of Richard's Hotmail
Sent: Saturday, September 27, 2008 3:49 AM
To: ddailey; <A HREF="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">whatwg at whatwg.org</A>
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 &quot;frame&quot; 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.

</PRE>

<!--endarticle-->
<!--htdig_noindex-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016318.html">[whatwg] WebSocket support in HTML5
</A></li>
	<LI>Next message: <A HREF="016351.html">[whatwg] WebSocket support in HTML5
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16329">[ date ]</a>
              <a href="thread.html#16329">[ thread ]</a>
              <a href="subject.html#16329">[ subject ]</a>
              <a href="author.html#16329">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
mailing list</a><br>
<!--/htdig_noindex-->
</body></html>

/lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-September/016329.html