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

multiple input connections #16

Open
chadrik opened this issue Aug 14, 2015 · 0 comments
Open

multiple input connections #16

chadrik opened this issue Aug 14, 2015 · 0 comments

Comments

@chadrik
Copy link
Contributor

chadrik commented Aug 14, 2015

We need to support input ports with more than one connection, which is part of the fbp standard. From the book:

Connections may have more than one input end, but they may only have one output. IPs from multiple sources will merge on a connection, arriving at the other end in "first come, first served" sequence.

In our case the order that the runtime chooses to process suspended upstream components influences the order, so it probably makes sense to execute them in the order they were connected.

The other question this feature raises is whether to allow multiple IIPs to be connected to an input, and whether to allow mixing of IIPs and component connections. IIPs are essentially components which generate a single IP before terminating (which is exactly what they are in pflow) so why should one not be able to connect multiple the same way that multiple components can be connected? I can already see use cases where we want a component to iterate over 2 or more known static values: connecting multiple IIPs would be the simplest solution.

@Flushot Flushot modified the milestone: Basic graph execution Sep 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants