{"id":8065,"date":"2015-11-23T18:40:05","date_gmt":"2015-11-23T18:40:05","guid":{"rendered":"https:\/\/unknownerror.org\/index.php\/2015\/11\/23\/how-to-identify-the-results-of-guzzle-multiple-requests-level-very-hard-open-source-projects-guzzle-guzzle\/"},"modified":"2022-08-30T15:03:02","modified_gmt":"2022-08-30T15:03:02","slug":"how-to-identify-the-results-of-guzzle-multiple-requests-level-very-hard-open-source-projects-guzzle-guzzle","status":"publish","type":"post","link":"https:\/\/unknownerror.org\/index.php\/2015\/11\/23\/how-to-identify-the-results-of-guzzle-multiple-requests-level-very-hard-open-source-projects-guzzle-guzzle\/","title":{"rendered":"How to identify the results of Guzzle multiple requests? (level: very hard)-open source projects guzzle\/guzzle"},"content":{"rendered":"

A. Summary<\/strong><\/p>\n

As its title, Guzzle allows to send multiple requests at once to save time, as in documentation.<\/p>\n

$responses = $client->send(array(\n    $requestObj1,\n    $requestObj2,\n    ...\n));\n\n(given that each request object is an instance of\nGuzzle\\Http\\Message\\EntityEnclosingRequestInterface)\n<\/code><\/pre>\n
When responses come back, to identify which response is for which request, we can loop through each request and get the response (only available after executing the above command):<\/p>\n
$response1 = $requestObj1->getResponse();\n$response2 = $requestObj2->getResponse();\n...\n<\/code><\/pre>\n
B. Problem<\/strong><\/p>\n
If the request object contains the same data. It’s impossible to identify the original request.<\/p>\n
Assume we have the following scenario where we need to create 2 articles: A and B on a distance server: something.com\/articles\/create.json<\/p>\n
Each request has same POST data:<\/p>\n
subject: This is a test article\n<\/code><\/pre>\n
After created, the Guzzle responses with 2 location come back:<\/p>\n
something.com\/articles\/223.json\nsomething.com\/articles\/245.json\n<\/code><\/pre>\n
Using the above method to link response-to-its-request, we still don’t know which response is for which article, because the request object is exactly the same<\/strong>.<\/p>\n
Hence in my database I cannot write down the result:<\/p>\n
article A -> Location: 245.json\narticle B -> Location: 223.json\n<\/code><\/pre>\n
because it can be the other way arround:<\/p>\n
article A -> Location: 223.json\narticle B -> Location: 245.json\n<\/code><\/pre>\n
A solution is to put some extra parameter in the POST request, e.g.<\/p>\n
subject: This is a test article\nrecord: A\n<\/code><\/pre>\n
However, the distance server will return error and does not create article because it does not understand the key “record”. The distance server is a third party server and I cannot change the way it works.<\/p>\n
Another proper solution for this is to set some specific id\/tag on the request object, so we can identify it afterwards. However, I’ve looked through the documentation but there is no method to uniquely identity the request like<\/p>\n
$request->setID(\"id1\")\n\nor\n\n$request->setTag(\"id1\")\n<\/code><\/pre>\n
This has been bugging me for months and still cannot resolve this issue.<\/p>\n
If you have solution, please let me know.<\/p>\n
Many many thanks and you’ve saved me!!!!<\/p>\n
Thanks for reading this long post.<\/p>\n","protected":false},"excerpt":{"rendered":"
A. Summary As its title, Guzzle allows to send multiple requests at once to save time, as in documentation. $responses = $client->send(array( $requestObj1, $requestObj2, … )); (given that each request object is an instance of Guzzle\\Http\\Message\\EntityEnclosingRequestInterface) When responses come back, to identify which response is for which request, we can loop through each request and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-8065","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/8065","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/comments?post=8065"}],"version-history":[{"count":1,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/8065\/revisions"}],"predecessor-version":[{"id":8653,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/8065\/revisions\/8653"}],"wp:attachment":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/media?parent=8065"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/categories?post=8065"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/tags?post=8065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}