On Thu, Mar 3, 2016 at 3:57 PM, Jim Jagielski <[email protected]> wrote:
> /** Config vector containing pointers to connections per-server
> * config structures. */
> struct ap_conf_vector_t *conn_config;
Yes, this is opaque, and turns out to be a implemented as void**.
We could even make it a struct if we'd want 2 "batons" per module,
with something like:
struct ap_conf_vector_t {
void *config;
void *context;
};
in server/config.c, without breaking the API (since it is opaque).
And then let ap_get_module_config/context() use the existing
conn/request_config.
Another vector might be better/simpler/safer, though.
Still I'm not sure to understand the use case for now...
