- From: Florian Bösch <pyalot@gmail.com>
- Date: Mon, 17 Sep 2012 15:24:58 +0200
- To: Joran Greef <joran@ronomon.com>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>
Received on Monday, 17 September 2012 13:25:31 UTC
On Mon, Sep 17, 2012 at 3:06 PM, Joran Greef <joran@ronomon.com> wrote: > You are conflating web apps (trusted, installed) with web pages (single > link click). > You should clarify that when you say "web-apps" you mean the other kind. > No, WebSockets are not "plain old TCP". > After handshake the pipe isn't handling any http anymore. It's just plain old TCP sending bytes in both directions, and you "select" by catching websocket events. You aren't even restricted to same-domain policies with websockets, only thing, you need a websocket ready listener on the other end, not just any open connection, so the handshake can proceed. > WebRTC is above UDP. It's not UDP. WebRTC is a massive conglomeration of > protocols and codecs and opinions. > Well you can be happy or unhappy with WebRTC, but WebRTC unreliable data channels *are* UDP. Instead of recvFrom you listen to channel events, but that's it. If you're not happy with WebRTC for UDP, go on and propose another standard that does it how you like it. > How do you fsync in a browser? > You mean you're not happy with the current state of browser supported file-systems. Fair enough, propose a better standard for that.
Received on Monday, 17 September 2012 13:25:31 UTC