fictorial
Feature Request : Support alternative client connection methods
I am just getting started experimenting with NodeRed (and Node). In my research I discovered Socket.IO-node which seems to implement a client connection using not only websockets, but multiple alternative long lived connection methods such as flash, long poll, etc. This would allow non-websocket enabled browsers to fall back to a connection that they can use.
http://github.com/LearnBoost/Socket.IO-node
If it works this is hugely desirable while most browsers still don't support WS.
Is it possible to have an integration with Socket IO that would gain all of the (as yet untested by me) fallback and connection goodness with the backend goodness of NodeRed?
In general it would seem desirable to be able to plug-in various client connection code to your backend.
Yes, another developer has done this work. It's in my Fork Queue. I'm not going to have time to review it until late next week.
http://github.com/saimonmoore/nodered/commits/master/
Hi guys, since I've tried getting nodered test client running under Adobe Air and Titanium Desktop, ive tested the fictorial / nodered branch code patched to use the Flash Sockets (web-socket-js here on github) and it works well with a simple patch/and importing the required JS code. If interested I can provide a diff file.
