[dev] CyrSQL and SQL driver

[Jan Schneider]

Zitat von Vilius Šumskas <vilius at lnk.lt>:

> Hi,
>
>> > Zitat von Vilius Šumskas <vilius at lnk.lt>:
>>
>> > As I said, if it's more work to change the sql driver to be more
>> > flexible than to make the cyrussql stand-alone, then go for it. :)
>>
>> I was thinking about this back and forth and was still not sure what
>> is the best way to handle all possible backend implementations (see:
>> http://marc.info/?l=horde&m=121447306525089&w=2 for example). I have
>> also  studied Cyrus driver and came up with the following idea:
>>
>> 1. Write couple of backend authentication "sub-modules" which
>> represents not the backend technology (e.g. SQL) but actual backend
>> used (e.g. Web-cyradm v.0.5.4 SQL Schema). They will have all necessary
>> methods for backend manipulation. These "sub-modules" will *not* be
>> listed under Authentication dropdown menu in Horde Configuration.
>>
>> 2. Rewrite/fix current Cyrus driver to allow the selection of
>> "sub-modules" as the backend in the Configuration.
>>
>> 3. Deprecate CyrusSQL driver.
>>
>> Is this good enough or I have overlooked something along the way?
>
> Can someone comment on this or should I proceed?

I'm having a hard time to really follow your problems in that thread.  
AFAIU the problem is with virtual domain support that has been added  
with 2.2? Can you summarize which consequences this had when  
authenticating Cyrus against SQL?

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/