-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On May 9, 2007, at 1:28 PM, Ben Gollmer wrote:
On May 9, 2007, at 12:25 PM, David Reid wrote:
It should be possible to use python-ldap[1] without any design
changes to the twistedcaldav.directory APIs however python-ldap is
not an asynchronous API so it's performance in our twisted server
may be suboptimal and require the use of a caching mechanism
similar to OpenDirectoryService's.
P.S. If anyone feels incredibly motivated to pursue any course of
action along the lines of implementing some sort of LDAP Directory
Service I'm sure it would be welcome.
I'd like to take a crack at it. I'm familiar with Python LDAP
programming, not so much with the calendar server's source
(although I have been using it for several months now). I'm also
interested in the potential of using other LDAP directories as
authentication backends.
I can see that I have to implement the methods in
twistedcaldav.directory.directory; anyplace else I should look to
get started?
The formal interface definition is in
twistedcaldav.directory.idirectory. You may also look at the
appleopendirectory source in that same directory.
- -David
"Usually the protocol is this: I appoint someone for a task,
which they are not qualified to do. Then, they have to fight
a bear if they don't want to do it." -- Glyph Lefkowitz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGQjMArsrO6aeULcgRAnMrAJ91Pb5b1JbGIVXoVgTKAEWCRXpAmACfQ1ps
c1uiNgHmVHCbANTH5KCEwq4=
=7cdW
-----END PGP SIGNATURE-----
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/calendarserver-users
