{"issue":{"pull_request":{"diff_url":"https://github.com/fabpot/Goutte/pull/29.diff","html_url":"https://github.com/fabpot/Goutte/pull/29","patch_url":"https://github.com/fabpot/Goutte/pull/29.patch"},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/1e1ceeb39866031496170d87cae919ef?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"1e1ceeb39866031496170d87cae919ef","url":"https://api.github.com/users/mtdowling","login":"mtdowling","id":190930},"milestone":null,"labels":[],"assignee":null,"updated_at":"2011-11-12T23:11:44Z","comments":5,"closed_at":null,"url":"https://api.github.com/repos/fabpot/Goutte/issues/29","body":"Here's how Goutte would look using Guzzle.  What do you think?","html_url":"https://github.com/fabpot/Goutte/issues/29","number":29,"title":"Replacing Zend HTTP client with Guzzle","id":2218192,"created_at":"2011-11-12T18:41:50Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/1e1ceeb39866031496170d87cae919ef?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"1e1ceeb39866031496170d87cae919ef","url":"https://api.github.com/users/mtdowling","login":"mtdowling","id":190930},"updated_at":"2011-11-12T23:11:44Z","url":"https://api.github.com/repos/fabpot/Goutte/issues/comments/2719895","body":"You're right.  Looks like it was fixed yesterday (https://github.com/kriswallsmith/Buzz/pull/11).  It also looks like Buzz currently supports only two kinds of clients -- file_get_contents and curl based clients.  file_get_contents requires ``allow_url_fopen = On`` and the curl implementation, of course, requires curl.\r\n\r\nAnother reason I think Guzzle would be a smart move for Goutte is because Guzzle manages persistent connections.  Goutte, being tool for scraping websites, is going to send a large number of requests in succession to the same server.  Buzz creates a new curl handle for each request, whereas Guzzle implicitly manages a pool of persistent connections that are reused when possible.  Using persistent connections will make Goutte more efficient, faster, cause less strain on a network (fewer TCP connections), and reduced load on the remote server.","id":2719895,"created_at":"2011-11-12T23:11:44Z"}}