Attention is currently required from: pespin.

View Change

1 comment:

• File s1gw/S1GW_Tests.ttcn:

  • Patch Set #1, Line 143: vc_conn := f_ConnHdlr_spawn(refers(f_ConnHdlr_pfcp_assoc_handler),

    I wonder why do you need to spawn a new ConnHdlr to do some non-session related stuff. […]

    `test_CT` is not connected to the PFCPEM, so they cannot communicate. Only `ConnHdlr` components can talk to the PFCPEM. This is why I am spawning a `ConnHdlr` here.

    I could connect `test_CT` to the PFCPEM, but this would be the only reason to do that: we do not run test logic directly in `test_CT`. Also, a `ConnHdlr` can re-use the existing API to send and expect PFCP PDUs, so this is more convenient.

To view, visit change 42493. To unsubscribe, or for help writing mail filters, visit settings.