Stephen McConnell wrote:
Berin Loritsch wrote:
Step two: Prepare all ECM depenedencies (and ECM/TestCase)
for release.
* All fully deprecated packages (like concurrent and
collections) get moved into a "compat" project that
exists strictly to provide a backwards compatibility
layer. The original location gets nuked.
Step three: Prepare all Fortress dependencies (and Fortress/XFC)
for release.
* Decide if we want to deprecate Pool (only used in ECM)
pool is used by excalibur-thread.
excalibur-thread is used all over the place.
what is the implication here?
Like I said "decide". That said, Excalibur Thread does have
some problems when the pool implementation truly blocks. It
hits a deadlock which is bad. The pool implementation that
it uses has an issue where the blocking breaks and then creates
a new instance even if it is above the maximum.
The Doug Lea utilities have a better and more flexible thread
pooling code. We may want to migrate toward that.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
