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

Scoped mode #68

Open
bergie opened this issue Apr 1, 2016 · 2 comments
Open

Scoped mode #68

bergie opened this issue Apr 1, 2016 · 2 comments

Comments

@bergie
Copy link
Member

bergie commented Apr 1, 2016

NoFlo 0.7 added support for IP Objects that can do flow isolation via scope: noflo/noflo#373 noflo/noflo#162

We should add an option to the MsgFlo runtime that would isolate and identify message-based execution using the scope instead of groups.

This should be an option so that users can switch to scopes with graphs that are fully utilizing the new Process API.

@jonnor
Copy link
Member

jonnor commented May 5, 2016

Why should it be an option, shouldn't we just use this always for NoFlo 0.7 ?

@bergie
Copy link
Member Author

bergie commented May 12, 2016

Yeah, I realized we may not need a mode for this. With NoFlo 0.7, always post the IP with scope, but also set brackets.

Then at the outport side see whether you still get it from scope, otherwise fall back to topmost bracket.

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

No branches or pull requests

2 participants