-
http://noflojs.org/documentation/protocol/
-
Should work with FlowHub
http://noflojs.org/documentation/protocol/
-
It would be nice to make PhpFlo a [Flowhub](http://flowhub.io) compatible FBP runtime by implementing the [FBP protocol](http://noflojs.org/documentation/protocol/). In addition to Flowhub, this would…
-
Adding [FBP Protocol](https://flowbased.github.io/fbp-protocol/) support for this runtime would enable lots of tooling, like:
* [noflo-ui / Flowhub](https://github.com/noflo/noflo-ui) for visual pr…
-
Right now anyone who can find the address/port of the service can connect. Which is obviously unsafe, especially once supporting adding components, as these may execute arbitrary code.
When access co…
-
Supporting the group information in JSON graphs would enable adding information like what components are in what physical places, or in same device(s)
-
When running fbp-spec against MicroFlo with a component that sends floats, the returned packet values are always `0`.
As seen in c-base/microflo-luftdaten#4:
fbp-spec:
```yaml
topic: ValueToFl…
-
☝️ Greenkeeper’s [updated Terms of Service](https://mailchi.mp/ebfddc9880a9/were-updating-our-terms-of-service) will come into effect on April 6th, 2018.
## Version **0.2.3** of [fbp-protocol-client…
-
Cause an FBP protocol error to happen. In this case through an unparseable data as an IIP
```
FBP MICROFLO RECV: { protocol: 'graph',
command: 'removeinitial',
payload:
{ src: { data: …
-
Currently "values" on "inport" of component:component message just takes an array of values. I think it instead should take an array of { "id": "my-id", "name": "MyHumanId" }.
The "id" would be what …