From: Francis Cianfrocca <garbagecat10@...>
Date: 2006-05-02T15:08:52+09:00
Subject: Re: [ANN] Net::LDAP 0.0.1

------=_Part_49762_1491009.1146550129948
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Yes, that's precisely the plan: the point of writing an LDAP server in Ruby
is that it would be so easy to extend, particularly by feeding it from
dynamic data. We have a particular interest in aggregating multiple
directories on the fly, and also augmenting directory entries with real-tim=
e
presence data. We already do this in C++ on another project, but Ruby is
just so much nicer.

On 5/2/06, Sam Roberts <sroberts@uniserve.com> wrote:
>
> Quoting garbagecat10@gmail.com, on Tue, May 02, 2006 at 06:00:28AM +0900:
> > * Please tell us if you would be interested in seeing a public
> >  release of the LDAP server.
>
> I would use an ldap server if it was toolkit for dynamic resolution of
> ldap queries.
>
> I have ruby code to read the OS X AddressBook database, but there is no
> way to share that info to other AddressBook users.
>
> I could write an LDAP server that published address info from my address
> book to the local network using LDAP, and others using AddessBook could
> subscribe to it. Very handy. Probably work cross platform with many
> different kind of apps. Why should you have to hire a sysadmin just to
> share your address book? Drives me nuts, but there are lots of client
> libraries for LDAP around... not so many servers.
>
> If you do make a server, I don't know your plan, but maybe you can keep
> use cases that involve serving dynamic data in mind - more like webrick
> and less like slapd written in ruby.
>
> Cheers,
> Sam
>
>

------=_Part_49762_1491009.1146550129948--