2 ms·
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
by 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 agoYou can use Dart instead of Javascript.
- deleted 14y ago[deleted]