Brian, Bertrand, and others are using (variations on in many cases)
mod_wombat right now, pulling it into trunk is good in the long term,
but it leaves some folks hanging.

I'm thinking we should maintain the mod_wombat tree as an external
backport to 2.2. It can use Brian's thread scope approach (thugh I
actually want to change it to add the pool still, and backport all the
rest of the trunk changes), and keep the apreq2 dependency, for
example.

Thoughts?

Reply via email to