[dev] CyrSQL and SQL driver

[Vilius Šumskas]

Hi,

Thursday, May 29, 2008, 11:34:04 AM, you wrote:

> 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?

-- 
Best regards,
 Vilius