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
