I created a web server using Chrome Packaged apps. The problem that I see repeatedly is that chrome.socket.accept () and chrome.socket.write () do not call the callback function. It usually works more or less reliably if the request speed is less than 1 request per second. If I go above this, I will start to see errors or missing callbacks.
I did similar tests with the Google webserver sample application ( https://github.com/GoogleChrome/chrome-app-samples/tree/master/webserver ). This problem has the same problem. Typically, a web server takes less than 100 requests before the web server stops responding. The easiest way to reproduce the problem is to use the Chrome browser as a client and hold the F5 key for a few seconds.
It would be advisable to have a sample application demonstrating how to create a reliable web server using chrome.socket. So far, I have tried several different workarounds to monitor the situation from the application itself and restart the socket when the socket stops working, but this is not easy, because there is no reliable way to check the connection status or the status of the last operation when the callback is not fired. I tried using the getInfo () method, but it always returns "connected = true" regardless of the situation.
I saw this on Windows 7 and Chrome OS (Chromebook).
source
share