Again, my suggestion is to limit this to api config, not general purpose settings such as timeouts, and also to not document this as a "user" feature rather an internal hook for api writing.
It gets complicated otherwise, as you've mentioned, and the primary goal is to address tls settings for docker and azure types. Starting with an internal beta approach solves the TLS problem simply and allows us to wait for users to ask before we make it more complicated. Right now, no user has asked to configure okhttp directly yet. Make sense? On Dec 2, 2014 3:53 AM, "Ignasi Barrera" <[email protected]> wrote: > I thought about where to hook the user config and chose to put it at the > end, to make sure it won't be changes by jclouds. This will also help > changing and improving the driver without worrying about breaking user > customizations. > > I like the supplier approach, but there are properties, such as timeouts > or the follow redirects flag, that are primitives. We won't be able to know > if they have been set by the user supplier or not and we might be changing > its config by mistake. > > — > Reply to this email directly or view it on GitHub > <https://github.com/jclouds/jclouds/pull/619#issuecomment-65199507>. > --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/619#issuecomment-65227422
