Thanks for all the information. I guess for now we'll just make it so that our native server also understand WebSocket protocol.
On Wednesday, October 7, 2015 at 2:42:03 PM UTC-4, Floh wrote: > > The problem is: when you have a 'native' server and client talking through > TCP sockets with each other everything will work fine, but compile the > client via emscripten and run in a browser, and the server will no longer > understand the client since the data will now be > WebSocket-protocol-encoded. So it's a bit more involved than just getting > your socket code compiled through emscripten, the server needs to implement > the whole WebSocket protocol (which thankfully isn't that complex). > > Am Mittwoch, 7. Oktober 2015 20:26:07 UTC+2 schrieb Boris Sergeev: >> >> And besides, I forgot to mention the server is running on Windows native, >>> not JavaScript, so that wouldn't work. >>> >> Not sure why it's relevant... If you emscript some code, you get JS out >> of it. If your JS is in the client, which uses some standard network >> protocols, why does it matter who handles it on the server? >> >> -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
