How to send concurrent requests?

[mxr576]

Is there a way to send concurrent requests and wait for their results in a same way as Guzzle supports?
Ex.: Load entities by ids in a function from on API that can only load entities one by one.

(#7 Might be related to this question.)

[mxr576]

Okay, it seems Httplug promises and \GuzzleHttp\Promise\settle() and \GuzzleHttp\Promise\unwrap() are working fine together, so let me rephrase my question. How can my code remain client agnostic if I would like to implement the above mentioned example with another client adapter? Should I require and use guzzlehttp/promises for curl, react and others too?

[mxr576]

Tested cUrl adapter, it seems this one also working with Guzzle promises (not so surprisingly). Haven't tested other one.

[dbu]

glad you found a solution. the recommended way of doing this is using the HttpAsyncClient with a request, which returns you a php-http/promise . see http://docs.php-http.org/en/latest/components/promise.html

(for background: there should be a PSR - or even better a PHP language level solution - for promises. a PSR once started but so far has not been released, so we had to do our own promises for php-http.)

[mxr576]

@dbu Any estimate when the "own promises for php-http" could actually happen? Is there a related issue that I can follow?

[dbu]

not sure i understand the question. the doc i linked explains how to use the php-http promises. they exist already, so nothing needs to "actually happen" ;-)

for the promise PSR, i don't think there is a single issue to watch, you'll have to watch the FIG announcements to see if something happens there.

btw, i noticed that there is another section in the doc on sending asynchronous requests: http://docs.php-http.org/en/latest/httplug/tutorial.html#using-an-asynchronous-client