John Baldwin wrote:
On Friday 15 December 2006 14:45, Julian Elischer wrote:
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.
See Section 9.3-9.12, UNIX Network Programming Vol 1 3e for more info.
generally we would use socket ops or ioctls for this sort of thing..
syscalls is not how they would normally be done....
I'll give a free paper cookie to the first person to actually go _read_ the
committed code and notice that, *tada*, aside from the sctp_send*(), and
sctp_recvmsg() functions, these are indeed library wrapper functions around
getsockopt() and setsockopt().
*blush*
it was the fact that they SAID they were syscalls that tripped me up.
I'll go shut up now..
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
