Roland, > The purpose of the auto-close is to free the underlying connection for > immediate re-use.
I understand. But that can't be counted on to happen (might not finishing reading data), so any robust application has to call releaseConnection() anyway (e.g., in a finally). Given that, I think it's better for the library to enforce doing it right, rather than smooth over such omissions, which can make buggy code look like it's working. (But I've drifted a bit. I'm not really trying to settle the "should frameworks compensate for programmer errors" debate. ;-) Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
