Hi Seb! :)
Of course, thanks for the suggestion!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sat, Oct 16, 2010 at 2:51 PM, sebb wrote:
> On 16 October 2010 13:10, Simone Tripodi wrote:
>> Thanks for the feedbacks Seb!!!
>> what about if I start implementing a propo
On 16 October 2010 13:10, Simone Tripodi wrote:
> Thanks for the feedbacks Seb!!!
> what about if I start implementing a proposal and then we
> progressively refine the design?
Fine by me.
But it might be better to look at how the Tomcat JDBC pool
implementation might be of use before polishing
Thanks for the feedbacks Seb!!!
what about if I start implementing a proposal and then we
progressively refine the design?
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sat, Oct 16, 2010 at 1:46 PM, sebb wrote:
> On 16 October 2010 06:18, Simone Tripodi wrote:
>> yes
On 16 October 2010 06:18, Simone Tripodi wrote:
> yes, understood and agreed.
> BTW I still find redundant that the same field, used with the same
> semantic, is present in Config,Pool and Factory, my proposal was about
> keeping the Config only - immutable fields can be declared there - and
> rem
yes, understood and agreed.
BTW I still find redundant that the same field, used with the same
semantic, is present in Config,Pool and Factory, my proposal was about
keeping the Config only - immutable fields can be declared there - and
remove config parameters from Factory/Pool, that will require
On 15 October 2010 17:01, Simone Tripodi wrote:
> Hi all guys,
> there are Generic(Keyed)ObjectPool(Factory) that (in pairs, Pool and
> related factory) share the same kind of information, replicated in the
> related Config class.
>
> I wonder if we can improve that design and remove that informat
Hi all guys,
there are Generic(Keyed)ObjectPool(Factory) that (in pairs, Pool and
related factory) share the same kind of information, replicated in the
related Config class.
I wonder if we can improve that design and remove that information
redundancy: I propose to keep the Config classes only, p
