On 05/05/2011 19:08, Phil Steitz wrote:
> Re performance, don't forget to add something that skips the synch
> in createDataSource - i.e., use a PoolingDataSource directly to
> avoid the thread lineup on getConnection due to that internal synch.
Just tested that locally. It doesn't help that much.
Hi Mark,
I'm not j.u.c guru but if you're pleased to share your thoughts, I
would be glad to provide at least feedbacks.
Looking forward to see j.u.c. in action in pool, thanks for taking care of it!
Have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, M
Hi all,
looks like I've been causing too much flares! :D
I understand your concerns, anyway, as in the subject, I just proposed
a *2.0-beta1* release, as a first - of many, maybe - intermediate step
before pushing the 2.0.
We could even downgrade it to alpha1, and warning users that APIs can
appea
On 5/5/11 10:12 AM, Gary Gregory wrote:
> On Thu, May 5, 2011 at 12:33 PM, Phil Steitz wrote:
>
>> On 5/5/11 9:20 AM, Gary Gregory wrote:
>>> I would like to propose an aggressive release schedule:
>>>
>>> - Push 2.0 out as a generified version of 1.5 ASAP and add/remove/fiddle
>>> nothing else. "
On 5/5/11 10:27 AM, Mark Thomas wrote:
> On 05/05/2011 18:21, Phil Steitz wrote:
>> On 5/5/11 9:42 AM, Mark Thomas wrote:
>>> On 05/05/2011 17:33, Phil Steitz wrote:
On 5/5/11 9:20 AM, Gary Gregory wrote:
> I would like to propose an aggressive release schedule:
>
> - Push 2.0 out
On 05/05/2011 18:21, Phil Steitz wrote:
> On 5/5/11 9:42 AM, Mark Thomas wrote:
>> On 05/05/2011 17:33, Phil Steitz wrote:
>>> On 5/5/11 9:20 AM, Gary Gregory wrote:
I would like to propose an aggressive release schedule:
- Push 2.0 out as a generified version of 1.5 ASAP and add/rem
On 5/5/11 9:42 AM, Mark Thomas wrote:
> On 05/05/2011 17:33, Phil Steitz wrote:
>> On 5/5/11 9:20 AM, Gary Gregory wrote:
>>> I would like to propose an aggressive release schedule:
>>>
>>> - Push 2.0 out as a generified version of 1.5 ASAP and add/remove/fiddle
>>> nothing else. "Just give me the
On Thu, May 5, 2011 at 12:33 PM, Phil Steitz wrote:
> On 5/5/11 9:20 AM, Gary Gregory wrote:
> > I would like to propose an aggressive release schedule:
> >
> > - Push 2.0 out as a generified version of 1.5 ASAP and add/remove/fiddle
> > nothing else. "Just give me the generics P L E A S E!" :) C
On 05/05/2011 17:33, Phil Steitz wrote:
> On 5/5/11 9:20 AM, Gary Gregory wrote:
>> I would like to propose an aggressive release schedule:
>>
>> - Push 2.0 out as a generified version of 1.5 ASAP and add/remove/fiddle
>> nothing else. "Just give me the generics P L E A S E!" :) Change deprecated
>
On 5/5/11 9:20 AM, Gary Gregory wrote:
> I would like to propose an aggressive release schedule:
>
> - Push 2.0 out as a generified version of 1.5 ASAP and add/remove/fiddle
> nothing else. "Just give me the generics P L E A S E!" :) Change deprecated
> documentation from "Will be removed in 2.0" t
On 5/5/11 8:54 AM, Simone Tripodi wrote:
> Hi all guys,
> some of us (me included :P) are waiting for pool with generics; now
> that the migration has been done, WDYT about releasing a beta1
> release?
> It is basically the latest pool-1.5.X API, but with generics, at least
> we can start playing w
I would like to propose an aggressive release schedule:
- Push 2.0 out as a generified version of 1.5 ASAP and add/remove/fiddle
nothing else. "Just give me the generics P L E A S E!" :) Change deprecated
documentation from "Will be removed in 2.0" to "Will be removed in 3.0".
- Next is 3.0: This
Hi all guys,
some of us (me included :P) are waiting for pool with generics; now
that the migration has been done, WDYT about releasing a beta1
release?
It is basically the latest pool-1.5.X API, but with generics, at least
we can start playing with it.
Thoughts? Just let me know, I can take care o
13 matches
Mail list logo
