You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the upcall handler, we need to use usrsctp_recvv to retrieve the next message once the SCTP_EVENT_READ has been raised. In order to optimise memory allocation, can we get a function that returns the size of the message we would receive in the next usrsctp_recvv call?
as its value, which is already defined in RFC6458. This could only be used with getsockopt().
The only thing I'm not sure about is how to handle the case where no next message is queued. Returning -1 from getsockopt() and setting errno to EAGAIN is something I want to avoid. So I think it might be good to define a constant SCTP_NO_MESSAGE which is used in nxt_flags. Any opinion on that?
When using the upcall handler, we need to use
usrsctp_recvv
to retrieve the next message once theSCTP_EVENT_READ
has been raised. In order to optimise memory allocation, can we get a function that returns the size of the message we would receive in the nextusrsctp_recvv
call?Something like this:
The text was updated successfully, but these errors were encountered: