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

[Luigi Rizzo]

On Fri, Dec 15, 2006 at 01:44:41PM +0000, Bruce M. Simpson wrote:
> Andre Oppermann wrote:
> >
> > What makes these sctp_* syscalls so special as opposed to their
> > generic and protocol agnostic counterparts?
> They're used for operations which do not have a direct correspondence in 
> the existing functions, i.e. connecting to multihomed peers, and dealing 
> with one-to-many sockets.

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 ?

	cheers
	luigi