Sebastien Roy wrote:
> On Fri, 2009-08-21 at 23:51 +0100, Ceri Davies wrote:
>
>> On Fri, Aug 21, 2009 at 02:43:19PM -0700, Rao Shoaib wrote:
>>
>>> Jim,
>>>
>>> I have been told that we can ask ISC to maintain backward compatibility
>&
] |
| inet_cidr_pton | Committed | Documented[5] |
| inet_neta| Committed | Documented[5] |
|__|___|___|
Rao.
James Carlson wrote:
> Rao Shoaib wrote:
>
>> James C
James Carlson wrote:
>
>
>> Since ISC does not guarantee that these
>> interfaces will not change in incompatible ways we do not want to make
>> that guarantee.
>>
>
> Are there any interfaces for which they make that guarantee? If there
> aren't any, then I suspect that the wrong test is
James Carlson wrote:
> Sebastien Roy wrote:
>
>> | inet_cidr_ntop | Volatile | Undocumented |
>> | inet_cidr_ntop | Volatile | Undocumented |
>> | inet_nsap_addr | Volatile | Undocumented |
>> | inet_nsap_nto
Darren Reed wrote:
> On 11/11/08 02:13 PM, Rao Shoaib wrote:
>>>>
>>>> *) To support evolution the interface is versioned.
>>>>Current versions are obtained via the macros
>>>> SOCK_UC_VERSION (upcall interface)
>>>>
Darren Reed wrote:
> On 11/11/08 11:57, Kais Belgaied wrote:
>> ...
>> *) In the initial design a socket module writer was allowed to
>> register it own
>>sonodeops. This facility was deemed unnecessary and problematic.
>> In the
>>current design module writer registers only one create fu
James Carlson wrote:
> Kais Belgaied writes:
>
>> *) A new down call sd_poll has been introduced. This down call support
>>polling when the protocol is doing it own buffering
>>
>
> Could we have a detail or two on that one? Does this work like
> poll(2), and how is it used?
>
Yes f
Erik Nordmark wrote:
>
> I saw an issue in the list for which I have a comment. The issue is
> djr-024.4.3.3 If it is possible that some protocols will or will
> want to
> support an unbind, isn't it better to provide sd_unbind() rather
> than rely on a magic combination of paramters t
Thanks Jim. We currently have two consumers that could use a plugin
capability, NL7C and KSSL.
Rao.
James Carlson wrote:
> The DACF facility that Garrett was referring to is configured in
> /etc/dacf.conf and is implemented in $SRC/uts/common/os/dacf.c.
>
> See "Extensions to Device Autoconfig