You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Currently the
EndStation
is holding theExecutor
used by theProtocolInterface
and there is no way to configure the name of thatExecutor Queue
.An EndStation should be able to support multiple
ProtocolInterface
(one perAVB_INTERFACE
of theControllerEntity
orAggregateEntity
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 sameExecutor Queue
or a shared one.Step 1:
Executor
when creating anEndStation
Step 2:
EndStation
with multipleProtocolInterfaces
and reference them when creating anEntity
The text was updated successfully, but these errors were encountered: