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 ...but I'll let Randall chime in too. :)
Thats a good place to look too... note that we do not conform yet to the latest socket api our sctp_connectx() does not accept an additional argument to return the sctp_assoc_t .. it will.. but I have to get to it first :-0 R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 <or> 803-317-4952 (cell) _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
