Resouce Itterators

[GrahamCampbell]

When will these be returning to guzzle 4? Could you suggest an alternative that would work with guzzle 4?

[mtdowling]

I don't really think the feature makes that much sense now that PHP has generators, which is why I left it out. I didn't really like how it was implemented either, so I'm not sure what the best design for it would be if it were brought back in some way.

On Jul 26, 2014, at 5:43 PM, Graham Campbell notifications@github.com wrote:

When will these be returning to guzzle 4? Could you suggest an alternative that would work with guzzle 4?

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

[GrahamCampbell]

Generators aren't an option for me since I need to support users on php 5.4. How will the new aws sdk be handling this?

[mtdowling]

We will be using a very specific data driven iterator approach for AWS. We've found that implementing a specific iterator class for AWS rather than trying to fit iterator logic into an abstracted iterator class (ala Guzzle 3) has yielded far simpler code. We are going to release code later this year once we have more of the release strategy worked out and get Guzzle commands stable.

[GrahamCampbell]

Cool. Thanks.

[Spea]

Are there any news about this? Would really appreciate it, if you could share some information about the iterators for AWS.

[mtdowling]

The AWS SDK iterators can be found here: https://github.com/aws/aws-sdk-php/tree/v3/src/Common/Paginator. Iterating over resources is going to be vey application specific. If there is a way to describe this in a general-purpose way that works for multiple services, then I would suggest that it should part of a separate package that uses a client rather than be part of the client itself.