Re: ok

On Wed, 9 Feb 2000, Federico Di Gregorio wrote:

> Date: Wed, 9 Feb 2000 09:56:32 +0100
> From: Federico Di Gregorio <fo...@mi...>
> To: David Leonard <dav...@cs...>
> Subject: Re: ok
> 
> hi,
> 
> Scavenging the mail folder uncovered David Leonard's letter:
> > On Tue, 8 Feb 2000, Federico Di Gregorio wrote:
> > > any news? just to know what do you think about...
> > 
> > okay, well i didn't have gtk handy so i couldn't really appreciate your 
> > gui client code... :)
> 
> well... at now the gui is a little bit flaky. 90% of my time goes into
> the classes and a framework to use ldap to administer all our (MIXAD LIVE)
> internal data: accounts, customers, jobs, etc...
> 
> > what do you think about writing an X500 class, instead of a purely LDAP class?
> > I mean, there's no way you'd write the functionality, but conceptually,
> > an X.500 directory is identical to the structure manipulated via LDAP.
> > Plus, it would give the library a more legitimate feel? And make it look
> > more standard. LDAP is actually a protocol, not a database you see.
> 
> i thought X.500 was heavy-weight and ldap the way to lighten it. 
> if implementing X.500 is no more difficult that implementing ldap
> i will do it. at now ldap is all what we need and i don't have the
> time do do *much* more work.
> 
> > you you have access to the x.500 standards? its published by x/open 
> > now, i think..
> 
> nope.
> 
> > more documentation needed really
> 
> i agree.
> 
> > otherwise, looks okay - but i still havent thoroughly looked at it all.
> > are you using it now for serious stuff?
> 
> yes. the framework outlined above. i have some python classes inheriting
> on the LDAPEntry: they represent the basic objects for the managment of
> our cutomers.
>  
> > what i meant by discuss the heirarchy was to split the cvs and distribution
> > up into two trees:
> > 
> > 	a c module directory
> > 	a python lib directory
> 
> as i did? (apart from the top-level configure.) it is the best way to do
> it. now the problem is the namespace. have you decided if you want to go
> the "compatibility" way (move ldap -> _ldap and "from _ldap import *" in
> ldap/__init__.py) or you prefer to separate the namespaces (i.e., the C
> module is still ldap and i use something different. note that i can't
> use LDAP, because some broken platform does not differentiate between
> ldap and LDAP.)
> 
> let me know,

I thought it would be best to call the C module 'cLDAP' (cf cPickle) or
'_ldap' (cf _tkinter). since you've already suggested the latter, we'll
go with that.

d

ps: i've cc'd this to the developers list.

--
David Leonard                           Dav...@cs...
Dept of Comp. Sci. and Elec. Engg   _   Room:78-624  Ph:+61 7 336 52447
The University of Queensland       |+|  http://www.csee.uq.edu.au/~leonard/
QLD 4072  AUSTRALIA               ~` '~ E2A24DC6446E5779D7AFC41AA04E6401

Hey you! Don't disrespect our legal system. Ours is the best legal system 
that money can buy. - Anonymous Coward