> I am not sure why Socket is used. It was used in the first version > checked into CVS > (http://cvs.apache.org/viewcvs.cgi/xml-soap/java/src/org/apache/soap/uti > l/net/HTTPUtils.java?rev=1.1&content-type=text/vnd.viewcvs-markup). > Maybe it was because HTTP is relatively easy to implement, or maybe it > was a preference to not rely on the implementation of > HttpURLConnection, which might not be well optimized.
Through osmosis of reading this mailing list, I've come to believe (with no specific evidence to back me up) that it was done this way because various JDKs had bugs in the HTTP implementations that folks didn't like. Be that as it may, the current implementation is fairly inconvenient for incremental modification because HTTPUtils is fairly tangled up with SOAP stuff and is not really a standalone set of HTTP utilities. That makes replacing it with some other HTTP implementation quite a bit of work. Still, it could be done. An industrious person could try to refactor a lot of that code so that it did have more well-defined boundaries. In that case, it would probably be a lot easier to experiment with featurettes like HTTP redirects. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
