[dev] preferences naming is not ldap compliant.

[KaalH!]

I first try the preferences renaming approach, because it's easy, and doesn't 
decrease performance.

But ... change preferences names makes upgrade harder for people not using 
ldap.

Then, Atif Ghaffar (thanks Atif ;) proposed the mapping approach (cf message 
#3846 of this list). like him, I think this is more flexible, and I decided to 
write it.

Use a mapping hash lets programmers freely choose the preferences names 
without knowing anything about backends naming contraints.

This mapping is not really needed for sql, and not at all for session 
backend... 
But, if someone plan to write a remote XML based preferences backend (via XML-
RPC/SOAP/.NET ...), or an ICAP backend, etc... , mapping can be really useful.

My proposal for ldap schema is here : http://kaalh.smol.org/horde/horde.schema

-- 
Kaalh

Surlignage Chuck Hagenbuch <chuck@horde.org>:

> Quoting Jon Parise <jon@horde.org>:
> 
> > Yeah, the LDAP preferences need an overhaul.  I'll try and handle
> > this over break.  Actually, if we can decide on a schema here
> > (being that's the part with which I'm least experienced), I'll
> > take care of all of the coding and testing.
> 
> Since you're doing it, it's up to you, but can we not go with full-fledged 
> mapping of each and every pref attribute? Translating '_' to '.' makes much
> 
> more sense to me, and simply renaming prefs like '24hr' to be compliant...
> 
> -chuck
> 
> --
> Charles Hagenbuch, <chuck@horde.org>
> "What was and what may be, lie, like children whose faces we cannot see, in
> the
> arms of silence. All we ever have is here, now." - Ursula K. Le Guin
> 
> -- 
> Horde Developers mailing list: http://horde.org/
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe@lists.horde.org
> 
>