In a very large project I am a senior on, I use to be using HTTPClient v0.3-3
(www.innovation.ch/java/HTTPClient/).
b) After looking at the code to try to fix the problem, not only did I give up
trying to fix the problem, but I also gave up on the product :)
Yes, I went through exactly the same process. I needed preemptive
authorization which turned out to be a nightmare to add to the
innovation HTTPClient but oh so easy to add to Jakarta HttpClient.
I want to point out that I encountered bug 13463 early on, and after reading
the bugzilla db, I tried the patch attached to the end of it. I would just
like to give my vote to include it into CVS, as it fixes the problem (bug
13463) perfectly.
Its a pretty good sign when you start using a new product and they
already have fixes for some of the bugs you find! The development team
here working on HttpClient is better than any other team I have been
involved with in my corporate life.
As for bug 16458, I have fixed it.
It was a rather simple bug, and can be reproduced by closing the server side
socket while the client is still waiting for a response. This will cause the
client to take 100% cpu, and it will do so for ever and ever.
Its great you made that connection which would have gone unnoticed. I
would probablly have had to mark that bug as "works for me" otherwise as
it was apparently inadvertently fixed.
I have another bugfix that I will post in my next message.
Looking forward to it.
Jandalf
HttpClient release prime.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
