On 02 Mar 2016, at 2:26 AM, Yann Ylavic <ylavic....@gmail.com> wrote:
>>> Would it make sense to add a vector of contexts that same way we have a >>> vector of configs, one slot for each module, which will allow any module to >>> add a context of it’s own to conn_rec without having to extend conn_rec? >> >> Can't the existing ap_[gs]et_module_config(c->conn_config, ...) be >> used for that purpose? > > I mean, put the context in the module config? If we can it would be great - but is there an API guarantee that the memory pointed to by the config is a per-connection copy of the config, and not the raw underlying server wide config instead? Regards, Graham —
