Yes, the socket.io libs are just too big for Espruino (even the slim one seems to be 50kB!). I can't find any documentation at all on the actual low-level protocol either - so I think your best bet would be to have Espruino connect straight to a Node.js server.
Espruino's socket implementation is designed to be a cut-down version of Node's, so if you take a look at http://www.espruino.com/Internet#socketsĀ then you should be able to run the 'server' code on the server, and the 'client' code on Espruino - basically without modification.
Your other option I guess is to run MQTT on your server, and to bridge it with socket.io. It might be an easier way to ensure everything stays as individual packets, since the socket's just a stream of bytes, and there is no guarantee that sending abcdef won't result in two callbacks, one for abc and one for def.
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.
Yes, the socket.io libs are just too big for Espruino (even the slim one seems to be 50kB!). I can't find any documentation at all on the actual low-level protocol either - so I think your best bet would be to have Espruino connect straight to a Node.js server.
Espruino's socket implementation is designed to be a cut-down version of Node's, so if you take a look at http://www.espruino.com/Internet#socketsĀ then you should be able to run the 'server' code on the server, and the 'client' code on Espruino - basically without modification.
Your other option I guess is to run MQTT on your server, and to bridge it with socket.io. It might be an easier way to ensure everything stays as individual packets, since the socket's just a stream of bytes, and there is no guarantee that sending
abcdef
won't result in two callbacks, one forabc
and one fordef
.