Attention is currently required from: laforge, pespin.
1 comment:
Patchset:
Can't gen_sctp:send be used in some sort of non-blocking way?
There is an option to make send non-blocking by sending `non_block_send`, but then we still need a logic that would (periodically?) try to send again. With all these layers of abstraction (gen_sctp), we cannot know when the socket becomes ready for sending :/
Having N processes sleeping waiting to write to a socket sounds like a bit of a nightmare to me tbh, with eg. messages inside the proxied SCTP conn being reordered, etc.
This approach definitely needs careful thinking and planning. I am also a bit afraid of the complexity this would bring, especially given that the S1AP spec. explicitly requires the message ordering to be preserved.
To view, visit change 39666. To unsubscribe, or for help writing mail filters, visit settings.