Attention is currently required from: pespin, daniel.

View Change

2 comments:

• Commit Message:

  • Patch Set #3, Line 9: int

    in

• File include/osmocom/core/osmo_io.h:

  • Patch Set #3, Line 46: * Needs to return the size of the next segment. If it returns

    Maybe the initial point here is that I'm not sure why the segmentation callback is needed in osmo_io […]

    pespin: The point of osmo_io is to be a one-stop shop for all users of the kind of telecom protocols that we see - irrespective of whether they're on SEQPACKET bearers like SCTP or on the cumbersome "preserve message boundaries over TCP stream" approahc that IPA does. This significantly unifies code that has to deal with both variants, such as e.g. a BSC speaking BSSAP over either M3UA/SCTP or over IPA. The user should be concerned with sending or receiving protocol-level messages, and not be botered with TCP stream segmentation.

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