Attention is currently required from: dexter. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33898 ) Change subject: S1AP_Emulation: improve accessibility of unit-data ...................................................................... Patch Set 2: (1 comment) Patchset: PS2: 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 https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33898 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ttcn3-hacks Gerrit-Branch: master Gerrit-Change-Id: I041b45b247e365b0d4ee8645c07dc5f26007af82 Gerrit-Change-Number: 33898 Gerrit-PatchSet: 2 Gerrit-Owner: dexter <pmaier@sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge@osmocom.org> Gerrit-Reviewer: pespin <pespin@sysmocom.de> Gerrit-Attention: dexter <pmaier@sysmocom.de> Gerrit-Comment-Date: Mon, 24 Jul 2023 13:07:54 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Gerrit-MessageType: comment