Let me take a pragmatic view here: Oleg is the guy that will do most of
the
programming for 4.0. He's been waiting for this chance to overhaul the API
for years, and he's eager to finally use java.nio features. I think we
should let him have his way :-)
I agree that NIO is likely to provide enough benefits to justify requiring Java 1.4 - but I definitely like the idea of making
it reasonably possible for people to provide a 1.3 compatible implementation as well.
Adrian Sutton has made valid points about 1.3 compatibility, and being one
of Ye Old Ones (aka committers ;-), his voice will not go unheard.
Heh. I wouldn't give me so much credit - I haven't done any work to justify it in quite a while. Besides, the culture within HttpClient is that every voice is as important as others whenever possible.
So I
currently think the best way is to unleash Oleg on a 1.4 version and make
it as easy as possible to backport to 1.3. But the development effort for
the 1.3 version will have to come from people that actually want to or
have to use HttpClient on a 1.3 platform.
I'd agree with that. If I turn out to be the only one who needs 1.3 compatibility it should be up to be to implement it (or better yet, use it as leverage to get my boss to allow me to drop 1.3 support).
Development of a version that does not offer new features but has additional requirements is not likely to happen. At least it would have to be way faster (which could be considered a feature) to make the effort worthwile.
I also tend to think that HttpClient 5.0 will be out long before Java 5 is comprehensively used enough for requiring it to be advisable.
cheers, Roland
Regards,
Adrian Sutton.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
