Attention is currently required from: dexter.
1 comment:
Patchset:
I'm am wondering if a separate table is making things more complicated than needed. We could simply broadcast unitdata to all components, or we could introduce an "expect" mechanism where the handler component can indicate is is expecting data matching a certain template to arrive. I think both paradigms are used in different of our TTCN3 protocol stacks so far. A separate list of "componentes interested in unitdata" is new.
If you're worried that unexpected unitdata would upset existing test cases (if broadcast to all components), we could also introduce a separate/new port to handle only unitdata. If a test doesn't care about what arrives on that port, it simply never reads/receives from it.
To view, visit change 33898. To unsubscribe, or for help writing mail filters, visit settings.