-
For quick & dirty work, for instance when prototyping, it can be very useful to have a MsgFlo participant based on shell scripts, and mostly calling existing programs.
This can be done fairly simply …
-
It is important that people can communicate with MicroFlo programs from other things that NoFlo/JS. Adding a Python library would demonstrate that this is possible, and help people implement it for ot…
-
Would be needed for live-coding, adding/removing nodes in Flowhub.
Would need to handle both case of spawning something locally, and on a remote service like Heroku, which are quite different...
For …
-
Now coordinator crashes on malformed discovery messages, as reported in c-base/c-flo#35
```
May 14 03:31:26 c-flo node[3134]: Participant discovery failed: Discovery message missing .inports
May …
-
Cannot able to access environment variables in components
-
Should be documented somewhere proper, but here is good for now. Feel free to add comments!
Existing for MQTT transport
* [mqttwarn](https://github.com/jpmens/mqttwarn) has tons of protocol brid…
-
There are situations where we have MsgFlo participants are already bound to each other. The setup should not touch those, but know that the connection exists.
Example:
Foreign MQTT participants that…
-
It would be useful to have a tool that shows bindings between queues, and possible unconnected ones, and ones no longer connected in the graph
-
Modifying components is currently a very tedious and manual process. Ideally this is integrated in the UI/IDE.
- APIs needed in NoFlo WebSocket protocol. getsource/setsource, update component, progres…
-
Another list
* [Sonoff WiFi relay](https://www.itead.cc/sonoff-wifi-wireless-switch.html), ESP8266 programmable with Arduino