apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Bannert <aa...@clove.org>
Subject Re: PATCH: apr_reslist_invalidate
Date Wed, 10 Mar 2004 22:30:18 GMT
On Fri, Jan 02, 2004 at 03:09:09AM +0000, Nick Kew wrote:
> Rationale: if an module gets a resource that proves to be bad (e.g.
> a connection that's gone away), it shouldn't be returned to the
> pool to be given out again.  We should invalidate it.
> I'm proposing the following patch, though I'm not sure whether
> or not we should free_container in the event of destroy_resource
> returning an error(?)

Did this ever get committed? I don't see it in HEAD, so it seems like
it may have been forgotten.

FWIW, I'm +1 on the concept, and I'd be glad to test/commit. We'll
also want to add some test code while we're at it.


View raw message