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

Why are Netjack2 master ports marked Terminal? #133

Open
mildsunrise opened this issue Jul 18, 2015 · 0 comments
Open

Why are Netjack2 master ports marked Terminal? #133

mildsunrise opened this issue Jul 18, 2015 · 0 comments

Comments

@mildsunrise
Copy link
Contributor

Netjack2 creates from_slave ports and to_slave ports. Why are these ports marked as terminal? They are not edges of the graph; data coming at to_slave ports is processed at the slave and sent to from_slave afterwards.

It also makes sense if you think that the slave's client contains a sub-graph; data is processed by the sub-graph and returns to the master graph.

Sure, they are special ports because the data is not processed locally but sent over the network. Sure, data coming at from_slave is not necessarily related to to_slave. Still, a Netjack2 slave is intended (the docs insist on that) to do only processing and not interact with other soundcards or hardware.

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

1 participant