Hi folks! I hope you don't mind an "outsider" (with little-to-no experience in
OpenSource) contributing to this interesting thread.
[EMAIL PROTECTED] wrote:
> What's wrong with having multiple thread pools or db pools, each
> having special characteristics and working best in different situations ?
That it requires a special effort to find out which one fits your project
best. The classical problems of reuse multiply: it's not only fetch a library
and find out how it works, but fetch many libraries and find out how every one
work -- then research their strengths and weaknesses and choose the one that
suits you best. Now you can safely say that it seems less hassle just to write
your own.
If there must be different libraries doing the same things, it must be real
easy to choose the right one -- via documentation, benchmarks...
Cheers,
Alex.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
