directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <akaras...@apache.org>
Subject Re: DN serialization issues
Date Fri, 18 Feb 2011 23:24:47 GMT
On Fri, Feb 18, 2011 at 8:17 PM, Emmanuel Lecharny <elecharny@gmail.com>wrote:

> Hi guys,
>
> once upon a time, in order to improve the server permformance, the DN was
> serialized with its normalized value. This was to avoid a costly
> normalization when we pull back the DN from the backend. But now that we
> don't store anymore the DN into the entry, it does not make any sense to
> store the normalized DN.
>
> We should get rid of that.
>
>
+1



> Another problem is that the LogManager also serialize entries with a full
> DN on the disk, and when it reads them back, it should be able to inject the
> schemaManager into the DN, which is not done.
>
> All in all, the DnSerializer has nothing to do in the Ldap-API. It's a
> Server thingy, as is the EntrySerializer. Moreover, the DefaultEntry
> implements the Externalizable interface, but does also provides
> serialize()/deserialize() methods, which export the RDN, not the DN, simply
> because it's used only by the server.
>
> This is a mess...


Separating out the implementations might help decouple these server side
ONLY concerns. But I don't know how I feel about having to have a ServerDn
verses a regular Dn.

WDYT?

Alex

Mime
View raw message