In https://issues.apache.org/bugzilla/show_bug.cgi?id=42841 , Tom points out an issue that gives problems with MySQL (and possibly other DBD drivers) and suggests that a change to apr_reslist semantics would fix it. Tom also attaches a patch implementing his proposed change.
Prompted by a recent post to [EMAIL PROTECTED] concerning an old chesnut PR#37770, I see we have the same usage of reslist in managing proxy backend connections. Except that the mod_proxy documentation hints at precisely the behaviour Tom suggests: "ttl - ..... Apache will close all connections that has not been used inside that time period." Grammar aside, that suggests incorrectly that ttl can be used to prevent the server re-using a connection that's been idle for more than a specified period. If that were in fact how it worked, it could fix both bugs. Of course we can't just hack apr_reslist willy-nilly. But perhaps it's time to introduce an additional API, or even an environment variable, that will select the "maximum idle lifetime of a resource" semantics of TTL. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/
