Java 1.5 dependency for HttpCore NIO and eventually HttpAsync?

Folks,

I have been quietly working on the NIO based client in
HttpCore NIO and
kind of missed java.util.concurrent primitives a lot in the
process of
it. 

How would everyone feel about possibility of using Java 1.5
for HttpCore
NIO (and possibly HttpAsync as it would also benefit greatly
from using
java.util.concurrent code instead of home brewed sync
primitives)?

Oleg


------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org

--- Oleg Kalnichevski <olegkapache.org> wrote:

> Folks,
> 
> I have been quietly working on the NIO based client
> in HttpCore NIO and
> kind of missed java.util.concurrent primitives a lot
> in the process of
> it. 
> 
> How would everyone feel about possibility of using
> Java 1.5 for HttpCore
> NIO (and possibly HttpAsync as it would also benefit
> greatly from using
> java.util.concurrent code instead of home brewed
> sync primitives)?

At this point in time, I would say "go for it". It
is
new component, and would have clear benefits.

-+ Tatu +-



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection
around 
http://mail.yahoo.com 

------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org

+1

Maybe once a month check and see if the code works with Java
1.4 + this?

http://dcl.mathcs.emory.edu/util/backport-util-concurr
ent/

And it's Public Domain!!!


yours,

Julius


On Fri, 2006-29-09 at 20:16 +0200, Oleg Kalnichevski wrote:
> Folks,
> 
> I have been quietly working on the NIO based client in
HttpCore NIO and
> kind of missed java.util.concurrent primitives a lot in
the process of
> it. 
> 
> How would everyone feel about possibility of using Java
1.5 for HttpCore
> NIO (and possibly HttpAsync as it would also benefit
greatly from using
> java.util.concurrent code instead of home brewed sync
primitives)?
> 
> Oleg
> 
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
> For additional commands, e-mail:
httpclient-dev-helpjakarta.apache.org
> 
-- 
Julius Davies
Senior Application Developer, Technology Services
Credit Union Central of British Columbia
http://www.cucbc.com/
Tel: 416-652-0183
Cel: 647-232-7571

1441 Creekside Drive
Vancouver, BC
Canada
V6J 4S7


------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org

At the very least, there needs to be a 1.4.1 minimum
requirement for
NIO.  (1.4.0 had different behavior for how a selector
responds to
write interest -- it uses edged-triggered behavior [see:
http://www.keg
el.com/c10k.html#nb.edge ] on some OS's and
level-triggered on others.  1.4.1 made it level-triggered
everywhere.)

Sam

On 9/29/06, Tatu Saloranta <cowtowncoderyahoo.com> wrote:
> --- Oleg Kalnichevski <olegkapache.org> wrote:
>
> > Folks,
> >
> > I have been quietly working on the NIO based
client
> > in HttpCore NIO and
> > kind of missed java.util.concurrent primitives a
lot
> > in the process of
> > it.
> >
> > How would everyone feel about possibility of using
> > Java 1.5 for HttpCore
> > NIO (and possibly HttpAsync as it would also
benefit
> > greatly from using
> > java.util.concurrent code instead of home brewed
> > sync primitives)?
>
> At this point in time, I would say "go for
it". It is
> new component, and would have clear benefits.
>
> -+ Tatu +-
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
protection around
> http://mail.yahoo.com
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
> For additional commands, e-mail:
httpclient-dev-helpjakarta.apache.org
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org

Oh, whoops - I see that the backport has a different package
name:

http://dcl.mathcs.emory.edu/util/backport-util
-concurrent/doc/api/

But at least there's still hope for someone if they're
desparate enough.
So I'm still +1.


yours,

Julius



On Fri, 2006-29-09 at 11:34 -0700, Julius Davies wrote:
> +1
> 
> Maybe once a month check and see if the code works with
Java 1.4 + this?
> 
> http://dcl.mathcs.emory.edu/util/backport-util-concurr
ent/
> 
> And it's Public Domain!!!
> 
> 
> yours,
> 
> Julius
> 
> 
> On Fri, 2006-29-09 at 20:16 +0200, Oleg Kalnichevski
wrote:
> > Folks,
> > 
> > I have been quietly working on the NIO based
client in HttpCore NIO and
> > kind of missed java.util.concurrent primitives a
lot in the process of
> > it. 
> > 
> > How would everyone feel about possibility of using
Java 1.5 for HttpCore
> > NIO (and possibly HttpAsync as it would also
benefit greatly from using
> > java.util.concurrent code instead of home brewed
sync primitives)?
> > 
> > Oleg
> > 
> > 
> >
------------------------------------------------------------
---------
> > To unsubscribe, e-mail:
httpclient-dev-unsubscribejakarta.apache.org
> > For additional commands, e-mail:
httpclient-dev-helpjakarta.apache.org
> > 
-- 
Julius Davies
Senior Application Developer, Technology Services
Credit Union Central of British Columbia
http://www.cucbc.com/
Tel: 416-652-0183
Cel: 647-232-7571

1441 Creekside Drive
Vancouver, BC
Canada
V6J 4S7


------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org

(resend, as a virus has allegedly been detected in the
previous one)

> How would everyone feel about possibility of using Java
1.5 for HttpCore
> NIO (and possibly HttpAsync as it would also benefit
greatly from using
> java.util.concurrent code instead of home brewed sync
primitives)?

I guess by the time HttpAsync is ready for a beta release
we'll have Java 6 available and J2EE 5.0 as current.

+1

cheers,
  Roland


------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org

FYI, I've checked the Java requirements of a few other
projects:

Synapse requires Java 1.4
Axis requires Java 1.3, recommends Tomcat as platform
Tomcat 5.5 requires Java 1.5, or needs a 1.4 compatibility
package

We should try to restrict use of Java 1.5 to implementation
classes
and leave them out of the API. Maybe I'll split the Ant
build process
to compile API and implementation classes in two steps, so
we can
detect unwanted dependencies. One of these days, if time
permits.

cheers,
  Roland

------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org

On Sat, 2006-09-30 at 19:37 +0200, Roland Weber wrote:
> FYI, I've checked the Java requirements of a few other
projects:
> 
> Synapse requires Java 1.4

Roland, et al

As far as I know Synapse folks opted for implementing their
own HTTP
client. There is no point of sticking to Java 1.4 only
because of
Synapse. At the same time dependency on Java 1.5 can render
HttpCore
unusable for quite a few other projects, so going Java 1.5
may be a
little too aggressive. Let's see how things develop, and if
the
management of home brewed concurrent primitives gets too
expensive, we
can revisit this issue.

Cheers,

Oleg

> Axis requires Java 1.3, recommends Tomcat as platform
> Tomcat 5.5 requires Java 1.5, or needs a 1.4
compatibility package
> 
> We should try to restrict use of Java 1.5 to
implementation classes
> and leave them out of the API. Maybe I'll split the Ant
build process
> to compile API and implementation classes in two steps,
so we can
> detect unwanted dependencies. One of these days, if
time permits.
> 
> cheers,
>   Roland
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
> For additional commands, e-mail:
httpclient-dev-helpjakarta.apache.org
> 
> 


------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org

Oleg,

Although I personally love JDK 1.5 a lot, I see that many
people still 
must use JDK 1.4. Mostly because J2EE 1.4 is the most
prominent (Java) 
server technology used. J2EE 1.5 is still very young and
there is tons 
of 1.4 legacy code that needs 1.4 compatibility.

I suggest to use the 1.4 backport of the concurrent package
as mentioned 
by Julius Davies.

Odi

Oleg Kalnichevski wrote:
> Folks,
> 
> I have been quietly working on the NIO based client in
HttpCore NIO and
> kind of missed java.util.concurrent primitives a lot in
the process of
> it. 
> 
> How would everyone feel about possibility of using Java
1.5 for HttpCore
> NIO (and possibly HttpAsync as it would also benefit
greatly from using
> java.util.concurrent code instead of home brewed sync
primitives)?
> 
> Oleg
> 

-- 
[web]  http://www.odi.ch/
[blog] http://www.odi.ch/weblog/
[pgp]  key 0x81CF3416
        finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5
81CF 3416

------------------------------------------------------------
---------
To unsubscribe, e-mail: httpclient-dev-unsubscribejakarta.apache.org
For additional commands, e-mail: httpclient-dev-helpjakarta.apache.org