Hello Otis, > There is also a HTTPClient library at www.innovation.ch somewhere that > probably works with JDK 1.2.2 that you may want to use, instead of > hacking Jakarta's HTTP Client to support that version of JDK.
Hacking? My impression is that the usage of the two methods from JDK 1.3 in the HttpClient library were probably introduced there by accident. My only request is to revert the implementation to use methods that are also supported in a JDK 1.2. >From a pure Open Source perspective, one is very free to choose it's own toolset and to upgrade everything to the latest version at all times. In a commercial environment, this is definitely not the case! The mindset of not maintaining backwards compatibility is a VERY important reason why companies are scared to integrate OS code into there product. Imagine that we would have used the HttpClient library already in our development (VisualAge with 1.2 support) and that the 1.3 code crept in without notice... We would have two options: first, try to convince you (as I do know) to still support 1.2, or throw out the HttpClient library from our product. I prefer the former! To finish: I'm not against progress and evolution, but if you want to drop 1.2 support, first poll with your users before you do so! I can say that by the end of this year, we will probably have migrated from VisualAge to the new Websphere Developer product from IBM. Is it that hard to support 1.2 during that time? Yours sincerely, Ringo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
