Re: SCTP API section 7.1.13

From: David Lehmann <lehmann@ulticom.com>
Date: Wed Feb 16 2005 - 08:18:07 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) Randall Stewart wrote:
> That maybe.. or getsockopt() needs to be re-defined to require
> it to allow in-out parameters.. its that way on most
> BSD's but I don't think so on most other O/S's :-D

Agreed.

>> int sock_opt_info(int s, int level, int optname, void *optval, int
>> *optlen);
>>
>> The association id can be put in each structure so it could be used
>> in sock_opt_info(). Actually, the association id is in each structure.
>> Why is the association id needed on sctp_opt_info()?
>>
>
>
> Well, in the case of the 1-to-N model, you need to figure
> out which association id is being requested information
> on...

Isn't the association id in all of the structures used by
sctp_opt_info()?

> And put in most of the wording above verbatim.. with one
> minor change.. it will read:
>
> <t>
> For some IP stacks getsockopt() is read-only, so a new
> interface will be needed when information must be passed both in to
> and out of the SCTP stack. The syntax for sctp_opt_info() is,
> </t>
> <t>
> The sctp_opt_info() call is a replacement for getsockopt() only
> and will not set any options associated with the specified socket.
> A setsockopt() must be used to set any writeable option.
> </t>
>
> That hopefully will cover it :-D

Yep, looks good.

-- 
David Lehmann                          Ulticom, Inc.
AOL/Yahoo IM: davidULCM                1020 Briggs Road
1-856-787-2729                         Mt. Laurel, NJ 08054   USA

Received on Wed Feb 16 08:43:00 2005