3 ms·
Ot here, the network might be high performance but the socket API in Chrome need some fix. https://code.google.com/p/chromium/issues/detail?id=170595 https://c
by est 14y ago
Ot here, the network might be high performance but the socket API in Chrome need some fix.
https://code.google.com/p/chromium/issues/detail?id=170595 https://code.google.com/p/chromium/issues/detail?id=170595
the chrome.socket API is really awesome, it can listen to tcp/udp connections, works like a mini NodeJS. It's a shame they didn't make it more stable.
- kinlan 14y agoI coded that demo, it is not the Chrome Socket API that is the problem, it is that I don't error properly in the code and it blocks the port like any socket server would.
- est 14y agoThanks for the demo How to catch that error? There's no exception callback in the doc http://developer.chrome.com/apps/socket.html http://developer.chrome.com/apps/socket.html And if the port is already blocked, how to recover?