I have a question on emscripten's socket wrapper API behaviour for TCP sockets when doing send/recv:
Does one call socket send() call result in exactly one websocket send() call with the same data (so that I can do one send() per message, and the message arrives intact at the other side's recv)? The reason I'm asking is that I want to make use of WebSocket's implicit message framing, when the client is running in the browser and talks to a WebSocket-capable backend. If it is guaranteed that I can do one send() per message on the client side, and that entire data arrives atomically in one recv() on the server side I could skip the whole custom-message-framing that's necessary in native TCP sockets. I'm not sure if it is worth it yet, since it would result in 2 different code paths on the client side (harder to test for correctness), just something I'm considering at the moment since it would simplify the backend (written in Go, using the gorilla/websocket package). Cheers & thanks! -Floh. -- 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.
