- From: Marcos Caceres <w3c@marcosc.com>
- Date: Mon, 31 Mar 2014 13:40:47 -0400
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: sysapps <public-sysapps@w3.org>, Anders Rundgren <anders.rundgren.net@gmail.com>
On March 31, 2014 at 1:26:47 PM, Bjoern Hoehrmann (derhoermi@gmx.net) wrote: > * Marcos Caceres wrote: > >On March 31, 2014 at 11:44:11 AM, Anders Rundgren (anders.rundgren.net@gmail.com) > wrote: > >> It seems that the Raw Socket API can only be used by "trusted applications". > >> I don't know exactly what that is, or more specifically: who is > >> the trusting party? > > >We will try to make it web facing. > > There is extensive documentation on the web about experiences with that > in Java, Flash, and in the development of the Websocket protocol. There > is little reason to think browser vendors would make a raw socket API > available to web content without considerable evidence that it cannot be > used to attack intermediaries, among other things. Doesn't mean we shouldn't try or learn from those things if we are going to standardize such an API. We could, nonetheless, approach it from the other end and see if we can get support for Web Sockets or WebRTC data channels in the systems that TCP/UDP socket API would interface with.
Received on Monday, 31 March 2014 17:41:16 UTC