API draft: section 8.3 and 8.5

From: David Lehmann <lehmann@ulticom.com>
Date: Tue Feb 08 2005 - 09:25:39 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) Hello,

Sections 8.3 and 8.5 are not clear on exactly what structures are being
returned. It states:
    On return, addrs will point to a dynamically allocated array of
    sockaddr structures of the appropriate type for the socket type. The
    caller should use sctp_freeladdrs() to free the memory. Note that
    the in/out parameter addrs must not be NULL.

    If sd is an IPv4 socket, the addresses returned will be all IPv4
    addresses. If sd is an IPv6 socket, the addresses returned can be a
    mix of IPv4 or IPv6 addresses.

IMHO, something similar to the following would be more explicit:
    On return, addrs will point to a dynamically allocated array of
    sockaddr structures of the appropriate type for the socket type.
    If sd is an IPv4 socket, 'addrs' will point to an array of struct sockaddr_in
    and the addresses returned will be all IPv4 addresses. If sd is an
    IPv6 socket, 'addrs' will point to an array of struct sockaddr_in6 and the
    addresses returned will be IPv6 addresses and/or IPv4 mapped addresses.

    The caller should use sctp_freeladdrs() to free the memory. Note that
    the in/out parameter 'addrs' must not be NULL.

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

Received on Tue Feb 8 09:52:11 2005