Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What to do with connection capacity #1

Open
jpaulm opened this issue Oct 7, 2014 · 3 comments
Open

What to do with connection capacity #1

jpaulm opened this issue Oct 7, 2014 · 3 comments
Labels

Comments

@jpaulm
Copy link
Owner

jpaulm commented Oct 7, 2014

In the pre-NoFlo version of .fbp notation, connection capacity was indicated by a number in brackets immediately following the arrow (->). NoFlo JSON has no provision for connection capacity AFAIK, although @bergie has suggested using metadata within the component part of a process specification.

  • where do we specify capacity in .fbp notation?
  • where should it be specified in the JSON output?

Refs: noflo/noflo-ui#371, noflo/noflo-ui#370, jonnor/javafbp-runtime#2

@jpaulm jpaulm added the question label Oct 7, 2014
jpaulm pushed a commit that referenced this issue May 30, 2016
@dancrumb
Copy link
Contributor

dancrumb commented Jun 7, 2016

Did you settle on anything here?

TBH, I think the notation is well understood (capacity in brackets) and I think support in this parser doesn't undermine NoFlo.

We could 'enable' or 'disable' support in the parser with a parameter, so that we can maintain parity with NoFlo.

@dancrumb
Copy link
Contributor

dancrumb commented Jun 7, 2016

Looks like the only question is outputting capacity, right?

https://github.com/jpaulm/parsefbp/blob/master/script/fbpscan.js#L205

@jpaulm
Copy link
Owner Author

jpaulm commented Jun 7, 2016

Sorry, I've been out all day, and have to head out again! Looks like connection metadata in the JSON is shaping up to be keyword-based, so I'm easy about how to encode capacity... :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants