>
> Unfortunately, there is no such thing as a "neutral shared utility".
Fact: CPAN works. And it is exactly that, "neutral shared utility".
If it is possible to do it for perl ( where everything can be done in many
ways - by design ), it should be possible in Java ( OO, etc ).
> Fast forward six to twelve months. Where do you think you will be? For
> insight on where I think you will be, take a peek at
It doesn't matter where we will be - the code will still be in the
repository. It may change, of course - and people who are using it will
have to make sure their code still works, and either fight against the
change ( -1 ), or change their code, or just create another util doing the
same job in the way you need.
Yes, it'll be duplication - but you can say "duplication is bad" or
"having multiple choices is good". I prefer the latest.
What's wrong with having multiple thread pools or db pools, each
having special characteristics and working best in different situations ?
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
