Pagination about client HOT 8 CLOSED

I set the per_page to PHP_INT_MAX so we can get all the possible values with just one request otherwise which is cheaper than going page by page. the instances where pagination would break is when someone have a large amount of data but I'm not sure you can get more than a few dozens of Kb... nevertheless we would still need to implement pagination. do you have any suggestions on how to tackle it ?

from client.

That's one of the things i'm having trouble with in my packages too. :/

from client.

I'm going to take a look at how the aws sdk for php does it.

from client.

Since you're using guzzle 3, you can do the same as the aws sdk does, and use: https://github.com/guzzle/service/blob/master/Resource/ResourceIterator.php. I'm using guzzle 4 for my problem though. :/

from client.

I see it is using a static 200 now, but the actual page is not being specific, limiting users to 200 droplets. Should a page parameter be added to droplet getAll?

from client.

Does this issue apply anymore? The $per_page and $page variables exist for the getAll function.

from client.

The issue was rather about automatic pagination, so we could get all, and then the library would iterate over all the pages for us.

from client.

This issue appears to still be under discussion, so I thought I'd add some more info.

When querying https://api.digitalocean.com/v2/droplets, the DigitalOcean API returns a meta object with total key.

Retaining this meta value at the end of the getAll() request would make paginating the API much easier with this library and the package @GrahamCampbell developed (https://github.com/GrahamCampbell/Laravel-DigitalOcean).

If anyone has suggestions for paginating the API rather than setting a high $per_page variable, I'm all 👂.

from client.