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

Cannot create multiple EndStation in the same process #132

Closed
christophe-calmejane opened this issue Jul 12, 2023 · 0 comments
Closed

Cannot create multiple EndStation in the same process #132

christophe-calmejane opened this issue Jul 12, 2023 · 0 comments
Labels
enhancement New feature or request high priority High priority issue
Milestone

Comments

@christophe-calmejane
Copy link
Contributor

Currently the EndStation is holding the Executor used by the ProtocolInterface and there is no way to configure the name of that Executor Queue.

An EndStation should be able to support multiple ProtocolInterface (one per AVB_INTERFACE of the ControllerEntity or AggregateEntity attached to it, using some sort of internal mapping).

Also it would be best to be able to choose if each ProtocolInterface is using the same Executor Queue or a shared one.

Step 1:

  • Add the possibility to choose the Executor when creating an EndStation

Step 2:

  • Add the possibility to create an EndStation with multiple ProtocolInterfaces and reference them when creating an Entity
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request high priority High priority issue
Projects
None yet
Development

No branches or pull requests

1 participant