[erlang-bugs] inet:setops manual: {priority, Integer} is documented twice

[Ingela Anderton Andin]

Hi!

Well you are correct that was strange! Seems it happened when a 
user-contribution was merged, it must have been wrongly based or 
something. We will fix.

Regards Ingela Erlang/OTP team - Ericsson AB

On 08/18/2015 10:59 AM, Loïc Hoguin wrote:
> These are duplicated only in the SERVER SIDE part of the manual. :-)
>
> On 08/18/2015 10:58 AM, Ingela Anderton Andin wrote:
>> Hi!
>>
>> The ssl docs aim to have a list of common options (when there is no
>> semantical difference, but an option may be "duplicated" if they have
>> different semantical implications on the client and server side.
>>
>> Regards Ingela Erlang/OTP team - Ericsson AB
>>
>> On 08/18/2015 10:17 AM, Loïc Hoguin wrote:
>>> In that spirit, more options are duplicate in the SSL manual:
>>>
>>> man ssl
>>>
>>> Section SSL OPTION DESCRIPTIONS - SERVER SIDE
>>>
>>> {psk_identity, string()}
>>> Specifies the server identity hint the server presents to the client.
>>> {log_alert, boolean()}
>>> If false, error reports will not be displayed.
>>> {honor_cipher_order, boolean()}
>>> If true, use the server's preference for cipher selection. If false (the
>>> default), use the client's preference.
>>>
>>> Description differs very little this time though.
>>>
>>> On 08/18/2015 12:40 AM, Loïc Hoguin wrote:
>>>> http://www.erlang.org/doc/man/inet.html#setopts-2
>>>>
>>>> I think it refers to the same option, but as I am not sure what this
>>>> option does *exactly* I'm reporting a bug rather than fixing it.
>>>>
>>>> First time it mentions the option it says:
>>>>
>>>> {priority, Priority}
>>>>      Set the protocol-defined priority for all packets to be sent on
>>>> this socket.
>>>>
>>>> Second time:
>>>>
>>>> {priority, Integer}
>>>>      Sets the SO_PRIORITY socket level option on platforms where
>>>> this is
>>>> implemented. The behaviour and allowed range varies on different
>>>> systems. The option is ignored on platforms where the option is not
>>>> implemented. Use with caution.
>>>>
>>>> Second one sounds better though it's probably good to add it's for all
>>>> packets sent on this socket.
>>>>
>>>> Cheers,
>>>>
>>>
>>
>> _______________________________________________
>> erlang-bugs mailing list
>> erlang-bugs@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-bugs
>