Date: Thu, 1 Apr 2004 17:35:45 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Jacques A. Vidrine" <nectar@freebsd.org> Cc: Oliver Eikemeier <eikemeier@fillmore-labs.com> Subject: Re: nss_ldap broken Message-ID: <200404020135.i321ZjK6070338@apollo.backplane.com> References: <Pine.GSO.4.10.10403311642150.28223-100000@pcnet5.pcnet.com> <1080773331.1956.36.camel@server.mcneil.com> <20040401124519.GA12985@lum.celabo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:I don't know if you overestimate it or not for practical purposes, i.e.
:I'm not sure how many applications are actually affected. However, it
:makes me quite nervous. There are many uses of `plug-in' APIs that
:involve dlopen/dlclose of dynamic objects. So, I also think we should
:codify how these cases should be handled.
Ha. I think people know where I stand on NSS.
The CAPS (ipc) code in DFly is coming along nicely, and I just
finished a portable structural encoding for requests and responses
(it's a userlevel encoding. The actual syscall interface passes
opaque data and doesn't care what the message's format is).
The next step is to actually begin implementing directory services
with it in DFly.
The primary syscall interface for CAPS is now using XIO in DFly (which
is basically an encapsulation of Alan Cox's use of SF_BUF's, similar to
how his PIPE code works), so it would be easily ported to FreeBSD. The
syscall API isn't quite up to snuff yet, I need to change its cid's over
to use real file descriptros, but it's very close to what I wanted.
-Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404020135.i321ZjK6070338>