-
* Maybe also useful for integration with [MsgFlo](https://msgflo.org/docs/communications/index.html)
* TODO separate step - may need an additional component "msgflo-adapter"
* TCP-based, but can a…
-
Currently there is no way to know whether a particular device registered with Hono is alive or dead. It would be useful to add lifecycle events support.
Building blocks:
* Information on how oft…
-
Hi guys,
Hope you are all well !
I am giving a quick look at **krakend** and it inspired me the following notes that I wanted to share with you. The idea is to get your point of view/feedback ab…
-
I am working on a runtime for an home automation project and the way I did it I have specific nodes which I call hardware nodes representing the sensors/ actuators themselves created when the server r…
-
```json
{
"protocol": "discovery",
"command": "participant",
"payload": {
…
-
This functionality was roughed in noflo-runtime-msgflo, should be moved down from there
https://github.com/noflo/noflo-runtime-msgflo/blob/master/src/mount.coffee#L257
Needed so that noflo-nodejs and…
-
Happens both for inports and outports. Makes debugging for some projects really hard, cause cannot see the relevant data... Especially when one cannot go up to outside level, like in case of a graph m…
-
In MsgFlo for instance, sometimes the component source code is unknown (if component is declared directly, not via a handler). Right now that causes fbp-spec to fail, we try to get the source to find …
-
I wasn't sure where to file this as it isn't so much an issue with noflo-ui, but the flowhub.io service itself (for which I could not find a standalone git repo).
There appear to be two different c…
-
Hi,
I'm trying to setup msgFlo
I'm just following this https://msgflo.org/docs/usage/index.html.
I can setup the participants.
repeater(Repeat) OUT -> IN repeaterdup(Repeat)
In this graph…