Open jonnor opened 9 years ago
Right now have to use the programmatic API, or noflo-runtime-msgflo --option=inports.in.queue=foo
noflo-runtime-msgflo --option=inports.in.queue=foo
Using port metadata, would allow it to be visualized and edited in Flowhub, and be less verbose setup
Or perhaps queue name should only be in the outer (msgflo) graph definition? In which case it would be edge metadata?
Right now have to use the programmatic API, or
noflo-runtime-msgflo --option=inports.in.queue=foo
Using port metadata, would allow it to be visualized and edited in Flowhub, and be less verbose setup