Event Listeners for executeAll()

[Jeremy Lindblom]

It looks like event listeners for the executeAll() method are hard-coded to -9999 (see https://github.com/guzzle/command/blob/master/src/CommandToRequestIterator.php). What is the reason for this and should we make this more flexible?

[Michael Dowling]

This should definitely be improved, and I think it should be implemented the same way as how requests are sent in parallel. I bet the trait you created would work here.

On Apr 30, 2014, at 11:31 PM, Jeremy Lindblom [e-mail] wrote:

It looks like event listeners for the executeAll() method are hard-coded to -9999 (see https://github.com/guzzle/command/blob/master/src/CommandToRequestIterator.php). What is the reason for this and should we make this more flexible?

For example, I have a scenario where I'm doing parallel command executions, and I want to be able to handle the completed commands (and errors), but only after some other listeners have been run (e.g., ones that parse results/errors).

Am I missing something here, or do we need to improve this area?

—
Reply to this email directly or view it on GitHub.