On SCTP_NOTIFY_ASSOC_DOWN, the receive callback (recv_callback) gets called with zero information about usrsctp HOT 4 CLOSED

Does the server get the message sent by the client before the receive callback with NULL fires? I'm expecting to see a NULL as the last thing happening (like a recv() would return 0).

from usrsctp.

Yes, the message is fully received, no problems there. If this is expected behavior, I can certainly handle it, but I wasn't sure if the code I was looking at does what it does intentionally.

from usrsctp.

You need an indication that you will not receive anything further. In the socket API, the recv() call returns 0. We model this by also providing 0 in the length and the NULL pointer for the data. That is expected and allows you to do cleanup if needed.

from usrsctp.

Thanks for the info. Will close because works as designed.

from usrsctp.