On Friday, February 7, 2003, at 07:13 PM, Brett Knights wrote:
If HttpClient made jdk 1.4 a requirement then I think it would be the end of any possible usage for me. In some contexts, where it would be used on a server mostly, it could be done, but on the desktop, it's far more complicated.Would the intention of this be to reproduce the functionality of java.net.URI as found in J2SE 1.4?java.net.URI seems quite complete. If so how many people can't make the switch to 1.4? I am not using 1.4.x in producion yet but I have been doing all my development with 1.4.1 so at this point it is just a matter of mustering the energy for installing jdk's and running tests etc.
Is it really worth incurring the 1.4 upgrade hit for something as small as the URI class? Regardless of this point, given the turnaround of bug-fixing in the jdk generations, it would be foolhardy to assume that the URI class is feature complete and totally bug-free (especially given some of the subtleties). In jdk-land, if you have found a bug, you could have submitted it years ago and *still* be waiting for a fix. I think I would rather have control over something as fundamental as URI handling.
I could perhaps see the point of a move to jdk1.4 if it was because of some super-duper java.nio non-blocking wonderfulness, but for one class?
--
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]