-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: support for setting/obtaining SCTP PPID #343
Comments
Will you implement it? |
I can give it a try. |
Should we really implement this? Asking because we will have to have the counterparts for all other transports, and currently one can just prepend the PPID to the message itself and it should work. |
I think this can only be implemented for SCTP. So if you are trying to set this on a non-SCTP transport, it could report a non-fatal error. If you are using neat for an application especially using SCTP, it might be useful... So for example, if you are using neat to implement Diameter/TCP or Diameter/SCTP it would be useful, if in the case of Diameter/SCTP the corresponding PPID would be used. |
What do you mean with 'non-fatal error'? |
Rethinking... If a different transport is chosen, the application should not be notified. |
It is currently not possible to set/obtain SCTP PPID when using SCTP transport. It would be useful to have an option for setting/getting the PPID.
The text was updated successfully, but these errors were encountered: