Maarten, I don't agree. HttpClient wants to completely hide away the connection management from the user. This is successfully accomplished by using a custom SocketFactory.
Ok, that's cool. Could have thought of that. I had a socket to start out with, so that made it a bit awkward ;)
Ah, I will do just that. The only thing I changed was actually to register my factory for "https". Maybe I will register it later for something called myhttps. Though that seems something of a hack too. The actual code change in the library is about 10 characters.
PS I've changed Protocol.java and provided my own SocketFactory as was described in the above guide. Just to make sure: I do not need to donate any software to the apache foundation for doing this, don't I? Not that it would be helpful - it's very JCA provider and project specific.
There should be no need to tweak Protocol.java. You can always register a custom SocketFactory with the default protocols.
If you have modified any HttpClient library classes you must provide the source code of your changes in addition to the binary distribution of your product. There is no need to send that code to the Apache Foundation though.
Thanks for the answer, even if incorrect :). I will try to sieve through my code and check if there is something useful in there. If there is, I will ask my supervisor if I can release such code. Maybe an HTTPS with client authentication & HttpClient howto (+ sample) would be a good thing.
Thanks go to Ortwin & Michael for the answers.
Maarten
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
