I agree. I think 1.1 is old enough that it should be forgotten. Having said that, doing some minor refactoring work to make HttpClient work in 1.1 is certainly much better then reinventing the wheel.
I guess my intent is to encourage people to make their own 1.1 port of HttpClient. I was able to get the unit tests (local and no host) up and running in eclipse with 1.1 in about 15 minutes. This is not something that I would like to maintain alongside the standard HttpClient, but it certainly can be done.
Mike
Oleg Kalnichevski wrote:
NTLM & SSL as standard features would also have to go (there are some Java 1.1 compatible JCE & JSSE implementations but I do not know of any available under open-source licence)
In general the use of Java 1.1 should be strongly discouraged in my opinion. The users of legacy platforms like Mac OS < 10 and IE should feel the pressure to upgrade (side-grade in case of IE ;-))
Oleg
On Thu, 2003-07-03 at 19:34, Michael Becke wrote:
I was just looking at how much work is required to make HttpClient work in a 1.1 JVM. Suprisingly it would not be that hard. Mostly it would just require the 1.1 collections jar and some package import rewriting. There are a few things like GCed connection reclaiming in MultiThreadedHttpConnectionManager and the use of Socket.sendBufferSize() that would need to be removed but that's about it. Is there enough interest in 1.1 support for a semi-supported version?
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
