I agree with @andrewgarner (discussed on Skype) that it's very unlikely that we are going to extend to other 'Frameworks' for HTTP connections, but we can follow a similar approach to Capybara. 
Capybara uses CSS selectors by default, but you can switch to XPath just adding a parameter to the find method.
```ruby
page.has_selector?('p#foo')
page.has_selector?(:xpath, './/p[@id="foo"]')
```
User Faraday as an Standard for MAS is great, but opening our API for the long term is also something nice when the cost is small. 
We may can postpone the creation of wrappers because adding a wrapper to a Faraday connection should not change our codebase, and stick to an agnostic factory definition this way:
* Default behavior (creates a Faraday HTTP connection)
```ruby
Core::ConnectionFactory.build(:public_website)
```
which is equivalent to:
```ruby
Core::ConnectionFactory.build(:http, :public_website)
```
* Creates a SOAP connection
```ruby
Core::ConnectionFactory.build(:soap, :public_website)
```