I can deprecate the strategies (leave the original http client methods taking strategy as a parameter in for backward compatibility), refactor the client a little bit (making some methods public, some methods final) so that we can provide flexibility to users by enabling them to smartly subclass the client and add all the verification stuff just to the new client functionality (i.e. not pollute the deprecated strategies with it). OK?