em-http-request allows you to send multiple requests on the same EM::HTTPConnection object, which is mostly useful for pipelining. If the underlying TCP connection drops, it will be re-established if another request is made on the same connection object. In testing that a user of em-http-request correctly dealt with timeouts (by retrying the request on the same connection object), it was discovered that webmock does not correctly emulate the real-world behaviour of em-http-request, and the parsed response data was being sent to the wrong `EM::HTTPClient` instance. This commit provides a failing test case (along with a test case that succeeded already, to ensure the basic behaviour continues to work in the future), along with a small change to the adapter code to correctly handle the change in clients after a timeout.
…test against 0.4.18 on Ruby 1.8.7
…efore 0.8.7 is not supported yet.
…i.e. hash_including(:a, :b => :c)