Mladen Turk wrote:
William A. Rowe, Jr. wrote:
> I'd like to proceed with this at the end of the weekend, unless
> there is significant objection that we can't resolve.
>
> The one side effect; it's not possible to "FIX" any API until
> we release 2.0.0 - please take some time to look at the new API's
> and think through if they solve our challenges, or if they need
> to be more flexible.
>
IIUC 1.3 allows new functions added, correct?
Yes; not 1.3.1 though, so the API's should be complete from the start,
lest we land at 1.4.0 right away.
If that's the case I have something to add by tomorrow.
It's a new apr_pool API allowing to create 'detached'
or 'standalone' pools. Those pools don't have parent
and must be explicitly destroyed.
This is particullary useful for embedding apr in systems
with their own memory management (like Java).
We are doing some really weird tricks in
Tomcat and Mina just to deal with premature and zombie
memory access.
Sounds cool - looking forward to the patch!
