Re: Own pure Python parser for LDAPv3 schema support

[Jens V. <je...@zo...>]

well, for what it's worth, the schema.py and schema_tree.py demos in the=20=

Demo folder work very nicely against my test server (OpenLDAP 2.1.3).

as far as performance goes, the subjective performance seems to be the=20=

same as it was with the other implementation. not sure if that's any =
kind=20
of useful indicator, though.

i think this is great stuff. thanks michael!!! i plan on using this to=20=

offer select widgets in places where i had to rely on people typing=20
objectClass names into text boxes before...

jens


On Monday, August 12, 2002, at 04:42 , Michael Str=F6der wrote:

> HI!
>
> Please take note of the following check-ins related to LDAPv3 schema=20=

> support (see below).
>
> Tested on various servers:
> OpenLDAP 2.0/2.1
> IBM SecureWay
> Lotus Domino/LDAP R5(?)
> Novell eDirectory 8.6.1/8.7
> Novell Directory Server 4.16SP1, 5.0
> Siemens Dir/X (various unknown versions)
> Innosoft's IDDS 4.5.1
>
> There still might be some detailed issues.
> Reviews, profiling performance hot spots, testing, etc. is =
appreciated.
>
> If that code works reliably I will cvs remove schema support based on=20=

> OpenLDAP's schema parser from C _ldap.
>
> Ciao, Michael.
>
>
> -------- Original Message --------
> Subject: CVS: python-ldap
> Date: Mon, 12 Aug 2002 13:32:29 -0700
> From: Michael Str?der <str...@us...>
> Reply-To: pyt...@li...
> To: pyt...@li...
>
> CVSROOT: /cvsroot/python-ldap
> Module name:	python-ldap
> Changes by:	stroeder	2002/08/12 13:32:29
>
> Modified files:
> 	Demo           : schema.py schema_tree.py
> 	Lib/ldap       : schema.py
>
> Log message:
> Abandoned use of OpenLDAP's schema parser. Implemented own parsing =
with
> ldap.schema.split_tokens() and ldap.schema.extract_tokens(). Probably =
bad
> performance and robustness =3D> peer review needed.
>
> SubSchema.name2oid is now nested dictionary separated by schema =
element
> classes. This was needed since schema element names are reused for=20
> attribute
> types and object classes on e.g. Novell eDirectory.
>
>