4 ms·

So uhm, how does it handle sockets? I'm thinking of writing some kind of p2p as a webapp that would be universal but right now it seems my best option is webRT

by RRRA 14y ago

So uhm, how does it handle sockets? I'm thinking of writing some kind of p2p as a webapp that would be universal but right now it seems my best option is webRTC that, if I understand what I've read correctly, will require a complete handling of the streams on a server... EDIT: Or how does NaCl differ from FirefoxOS goals and why?

deleted 14y ago
[deleted]
otibom 14y ago
NaCl executes native code in a sandbox, while FirefoxOS gives a plethora of APIs to Javascript. The end is similar (web pages have access to much more) but the mean is different.
- jychang 14y ago
  *means are different as in "The ends justify the means". It took me a couple of reads to understand what you're saying.
est 14y ago
By using this http://developer.chrome.com/apps/socket.html http://developer.chrome.com/apps/socket.html I played with this API for a few days and here are my conclusions: 1. the socket.listen can not handle much concurrency. It's very easily DoS'd 2. javascript String and ArrayBuffer is PITA to mess with. I tried to write a partially working HTTP/1.1 server, all the encodings and string parsing made me give up. 3. calback style programming is the new GOTO
- jrockway 14y ago
  You can use Dart instead of Javascript.
  - deleted 14y ago
    [deleted]