Phil Steitz wrote:
Yes. It may be ultimately best to make this configurable. If you are
OK with this approach, what I suggest is that you open a JIRA ticket,
attaching a version of your patch that supports configurability. Open
the ticket against 1.3 for now but keep the patch as is (i.e. against
1.4 release branch).
+1. I think this is the way to go.
While I understand your use case and can see both sides of the issue,
I think that the 1.2/1.4-RC1 behavior is the better, more natural
default for the pool, so would like to keep things as they are now in
1.4-RC1 for 1.4.
Also +1. We can't optimise pool for every use case by default. It just
isn't possible. Configuration is the way to handle this.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
