cvs commit: src/lib/libc/net Makefile.inc sctp_sys_calls.c src/sys/sys param.h

[Julian Elischer]

Craig Rodrigues wrote:
> On Fri, Dec 15, 2006 at 05:57:04AM -0800, Luigi Rizzo wrote:
>> i think Andre's question was this:
>> normally we use {set|get}sockopt() to configure the socket
>> as desired for special features (e.g. multicast is one).
>>
>> Why is it undesirable to use the same kind of overloading
>> for sctp ?
> 
> I think some of the reasons for why a new sockets API
> was introduced for SCTP was outlined in:
> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctpsocket-14.txt

which says:
--------------
8.  New Interfaces

    Depending on the system, the following interface can be implemented
    as a system call or library function.
---------------
The latter is what I'd expect..

syscalls is 'unusual' and unique to this protocol.


> 
> ...but I'll let Randall chime in too. :)
>