Active
Project:
Http Client
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Mar 2012 at 02:05 UTC
Updated:
12 Jul 2012 at 15:11 UTC
You might be interested in the HTTP Parallel Request Library. Here is a link to the readme. It works in cases where drupal_http_request() fails. Just wondering if there is any reason why you don't use drupal_http_request?
Comments
Comment #1
basvredelingI've tested replacing curl_exec by a drupal_http_request. The response needs a bit of extra handling and the difference in time between curl_exec an drupal_http_request is minimal. In my tests drupal_http_request is a tiny bit slower on my local machine. Implementing httprl would require quite a big rewrite of the module I believe. Because the requests need to be queued instead of handled right away.
Comment #2
mikeytown2 commentedhttprl queues the requests and executes them all in parallel in the same request. If your looking to queue them up and run them in a separate request, that would require some extra work. I wouldn't call it a big rewrite though because you can create a background process to run the HTTP requests for you. Let me know if your interested. Also checkout http://drupal.org/project/background_process as our goals are the same and are slowing going to merge into one.
Comment #3
basvredelingI created a stub sandbox module. You can check it out here: http://drupal.org/sandbox/basvredeling/1677198
The drupal_http_request delegate is pretty functional. The httprl is only functional on a single request. httprl is a loose dependency, it's not required but if enabled takes precedence over both curl (in http_client itself) and drupal_http_request (the aforementioned delegate).
Comment #4
basvredelingI forgot to mention that the sandbox module is aimed at Drupal 6. But Drupal 7 shouldn't be very difficult to implement.