On Mon, 2011-05-16 at 19:24 +0000, KARR, DAVID (ATTSI) wrote:
> I'm looking at a situation where some client code in an app will be
> connecting to a server which will require a custom ssl socket factory, but
> other client code in the same app will be connecting to a different server,
> which will not require that custom ssl socket factory.
>
> I was thinking that I could create separate HttpClient objects at startup
> time for the two different circumstances, and one would get the custom ssl
> socket factory configured into its SchemeRegistry, and the other would not.
>
> Is that reasonable?
>
Yes, it is.
Alternatively you could register a custom scheme ('myhttps' for
instance) for those connections that are meant to use a custom ssl
socket factory.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
