httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail T." <>
Subject Re: Limitations of mod_dbd - single server per vhost
Date Wed, 22 Aug 2012 13:21:16 GMT
On 22.08.2012 07:24, Nick Kew wrote:
> The implementation needs object persistence, of the kind we have
> in the per-server configuration but not per-directory.  That was the
> original design constraint.
I'd say, my complaint was a little misunderstood. It is not, that I wish 
to see separate DBD-configurations per location/directory, though it may 
be a good thing too.

It is that I want to be able to use more than one server per vhost. This 
collection of servers can be maintained in the persistent object you had 
in mind, where the single server is maintained now.

Perhaps, the DBD-statements should begin accepting one more (optional) 
argument -- the server's label:

    DBDriver	first	freetds
    DBDriver	second	mysql
    DBDParams	first	"...."
    DBDParams	second	"..........."

Then RewriteMaps can then changed to operate thus:

    RewriteMap	first	"dbd:first:SELECT ...."
    RewriteMap	second	"dbd:second:SELECT ...."

I don't think, I'm the best person to implement this -- whoever 
"quick-hacked" the dbd-maps in recently is, probably, better positioned 
to do this ;-) My employer's needs here are satisfied for now -- we 
decided to use text-maps for local cache and thus need only a single 
dbd-map for talking to database (if the local cache fails). But I can 
give it a try, if no one else does.



P.S. BTW, I fixed the FreeTDS/Sybase driver 
<> for APR/APU 
somewhat -- it has been absolutely broken and unusable for years, no 
kidding -- but don't see any movement on the ticket... Does anyone care?

View raw message