Date: Fri, 15 Dec 2006 13:44:41 +0000 From: "Bruce M. Simpson" <bms@FreeBSD.org> To: Andre Oppermann <andre@freebsd.org> Cc: Randall Stewart <rrs@FreeBSD.org>, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, cvs-src@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/net Makefile.inc sctp_sys_calls.c src/sys/sys param.h Message-ID: <4582A6C9.8010009@FreeBSD.org> In-Reply-To: <4582A1E0.1050503@freebsd.org> References: <200612151201.kBFC1qEv006825@repoman.freebsd.org> <4582A1E0.1050503@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. See Section 9.3-9.12, UNIX Network Programming Vol 1 3e for more info. Regards, BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4582A6C9.8010009>