diff options
| author | Micael Karlberg <[email protected]> | 2018-07-19 16:39:13 +0200 |
|---|---|---|
| committer | Micael Karlberg <[email protected]> | 2018-09-18 14:50:18 +0200 |
| commit | 7a5b320b5bb5ec45b21839005e8538172908fb57 (patch) | |
| tree | a901cc18fb10ed7fe6352a0205456f89f378c29a /erts/doc/src/socket.xml | |
| parent | f0a2e68a31ac585780ad05f777f1b7551770420e (diff) | |
| download | otp-7a5b320b5bb5ec45b21839005e8538172908fb57.tar.gz otp-7a5b320b5bb5ec45b21839005e8538172908fb57.tar.bz2 otp-7a5b320b5bb5ec45b21839005e8538172908fb57.zip | |
[socket-nif] Add (partial) support for socket (level sctp) option associnfo
Added support for the SCTP option ASSOCINFO.
This option is a bit tricky. As the underlying structure (sctp_assocparams)
contains the assoc_id, it begs the question what happens if this option
is fetched for:
* The own assoc (which means that we might have the assoc id in the
descriptor and can initiate that part of the struct accordningly).
* Another assoc: From assoc A asks for info with assoc_id set to
that of assoc B.
* The "owning" endpoint.
* Another endpoint (an endpoint to which the assoc does not belong).
So, if the user calls socket:[getopt|setopt] for an association socket,
shall we require that the assoc_id field is set to -1? Or not set at all
and therefor filled in automatically by the nif-code?
And, if the user calls socket:[getopt|setopt] for an endpoint socket,
shall we require that the assoc_id field is set to a valid id? Or shall
it not be allowed?
Questions, questions...
OTP-14831
Diffstat (limited to 'erts/doc/src/socket.xml')
| -rw-r--r-- | erts/doc/src/socket.xml | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/erts/doc/src/socket.xml b/erts/doc/src/socket.xml index 4ecf35b8ed..3e8e7af5c6 100644 --- a/erts/doc/src/socket.xml +++ b/erts/doc/src/socket.xml @@ -137,6 +137,9 @@ <datatype> <name name="sctp_event_subscribe"/> </datatype> + <datatype> + <name name="sctp_assocparams"/> + </datatype> </datatypes> <funcs> |