httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@lyra.org>
Subject Re: [PATCH] ap_xlateattr_t for passing options to ap_xlate_open()
Date Wed, 24 May 2000 00:12:33 GMT
On Tue, 23 May 2000, Jeff Trawick wrote:
>...
> With the understanding that we don't have to try too hard to maintain
> binary compatibility, I'm happy to make ap_xlateattr_t transparent,
> which means we can ditch the ap_xlate_create_xlateattr() and
> ap_xlate_set_xlateattr_sb() functions.  The app should clear the
> ap_xlateattr_t, then set any fields corresponding to attributes they
> wish to specify.
> 
> What about retrieval (querying attributes)?  I can ditch
> ap_xlate_get_sb() and instead provide ap_xlate_get_xlateattr(), which
> will fill in an ap_xlateattr_t corresponding to the specified
> ap_xlate_t.  Any storage pointed to by the ap_xlateattr_t will be from
> the same pool as the ap_xlate_t. 
> 
> Does this seem reasonable?  Do you still have a desire to specify
> attributes directly in the parameter list to ap_xlate_open()?

Why deal with a structure just to pass some parameters? Yes: I favor just
adding parameters to ap_xlate_open().

Within minor releases, we can add extra parameters to new functions such
as ap_xlate_open2(). At the major release, we drop the openN() functions
and go back to a single ap_xlate_open().

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/


Mime
View raw message