We use the backport to support JDK 1.4 clients for some of our applications
and we have had no issues with it at all.
It would be good if we could support using java.util.concurrent if
available however (it should be slighty faster since it can take advantage
of the atomic operations in Java 5). Perhaps have a "jdk 1.4 build task"
that removed "edu.emory.mathcs.backport." from the imports?
Robert
|---------+---------------------------->
| | "Trustin Lee" |
| | <[EMAIL PROTECTED]|
| | m> |
| | |
| | 21/03/2006 08:35 |
| | Please respond to|
| | mina-dev |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc:
|
| Subject: Using backport-util-concurrent
|
>--------------------------------------------------------------------------------------------------------------------------------|
Hi everyone,
Peter posted a patch that enables us to plug various thread pool
implementations into the ThreadPoolFilter:
http://issues.apache.org/jira/browse/DIRMINA-184
The only problem is that this patch depends on java.util.concurrent package
which exists only in Java 5+. Fortunately, there's a backported
counterpart
for it:
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/index.php
We could introduce this new dependency to MINA and use its rich feature
until we migrate to Java 5 later.
This is a poll. Please post your comment. :)
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
