WebSockets has extra framing around each message, on top of pure TCP sockets including handshaking - which is string based message (HTTP headers).
Framing contain some data about type of message, its length and masking. That pretty much it.
I have implemented this protocol in C# .Net long time ago (when there was no SignalR and .Net 4.5).
Those guys have it, but their implementation is a bit surplus: https://github.com/einaros/ws
Here is some code for send/receive in .Net with dataframing I've made some time ago: http://moka.me.uk/files/wsreadwrite.txt
UDP is unreliable especially on embedded systems. What about just streamed TCP? Pure binary TCP stream? As starting point I believe is a good thing, will allow other developers to implement their data protocols on top of it.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
WebSockets has extra framing around each message, on top of pure TCP sockets including handshaking - which is string based message (HTTP headers).
Framing contain some data about type of message, its length and masking. That pretty much it.
I have implemented this protocol in C# .Net long time ago (when there was no SignalR and .Net 4.5).
Those guys have it, but their implementation is a bit surplus: https://github.com/einaros/ws
Here is some code for send/receive in .Net with dataframing I've made some time ago: http://moka.me.uk/files/wsreadwrite.txt
UDP is unreliable especially on embedded systems. What about just streamed TCP? Pure binary TCP stream? As starting point I believe is a good thing, will allow other developers to implement their data protocols on top of it.