httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Bannert <aa...@clove.org>
Subject Re: cvs commit: httpd-2.0 STATUS
Date Fri, 17 Aug 2001 15:54:11 GMT
On Fri, Aug 17, 2001 at 08:18:56AM -0700, Ian Holsman wrote:
> William A. Rowe, Jr. wrote:
> 
> >>jerenkrantz    01/08/16 17:26:38
> >>
> >>  Modified:    .        STATUS
> >>  Log:
> >>  Hello, Goodbye.
> >>   
> >>       * use apu_dbm in mod_auth_dbm
> >>           Status: Greg +1 (low-priority volunteer)
> >>  +        Justin says: "Seems like this is already there, so should we just

> >>  +                      remove the other DBM code in that file?  If you want

> >>  +                      to use gdbm, or dbm, etc, you should tell apr-util."
> >>
> >
> >I'm not sure about this.
> >
> >If a user has many (existing) gdbm user databases, but would rather use Berkley db

> >for caching performance in the bits like mod_ssl and mod_usertrack, why should we

> >cripple their auth_dbm?
> >
> >Bill
> >
> this would be better solved with apr-util allow multiple DB types to be 
> created
> (similiar to how SMS works)
> 
> maybe a apr_dbm_create_gdbm()
>     apr_dbm_create_berkley_db()
>     apr_dbm_create_ndbm()
> set of routines is required
> 

If the application knows which dbm they want, they might as well just use
that API directly. The way I see it, APR is for when you don't care what
dbm is there under the covers, as long as your code works everywhere.

-aaron

Mime
View raw message