Is it possible to set a maximum number of results on a list page? Current value is 20 results per page and I want to change it.
Un film, une émission télévisée ou un artiste est introuvable ? Connectez-vous afin de créer une nouvelle fiche.
Vous souhaitez évaluer ou ajouter cet élément à une liste ?
Pas encore membre ?
Réponse de Travis Bell
le 10 septembre 2013 à 10h01
Hi BinaryFork,
No, it is not possible to increase the page size.
Réponse de xanderstrike
le 26 février 2014 à 19h40
Sorry to resurrect an old topic. Is this a feature on the roadmap?
I'm trying to to inner join the results of a similar_movies query with movies already present in my DB and it would be extremely helpful to be able to pull down 100 movies all at once instead of 20 five times. It'd be easier on you guys too.
This ought to be a trivial change on your end as well, just setting the limit to a parameter page_size (like page) and having a sane maximum (like 100).
Réponse de Travis Bell
le 27 février 2014 à 16h32
That's ok, but no it is not. We're content to keep it as is.
Cheers.
Réponse de xanderstrike
le 27 février 2014 à 18h22
Care to share why? This would be super helpful in a lot of applications, and shouldn't be that hard to implement.
Réponse de Travis Bell
le 28 février 2014 à 09h46
It's not a matter of how easy it is, it's to do with how practical of a feature it is vs. the performance side affects. The way we see it is you have two common use cases (looking at the majority of how users use our data):
Search results. Search is almost universally showing the results you're looking for within the first 20 items. If it's not, the problem isn't the page size, it's your search query. Over 98% of users never hit page 2 on our own website and we only show 10 results! 20 is more than enough.
Misc. list pages like top rated, popular, now playing. The first common use case would be if you're bringing the data in house. Limiting the pages to 20 items has little bearing on anything but a few extra requests. We cap these requests to 1000 pages so 20,000 items. Having some kind of a background job process these is trivial. The second common example would be a mobile app of a sort. There are many apps that support the "infinite" scrolling concept and this is quite simply, the smarter way to build your app anyways. It keeps the requests fast and short and we are only ever loading what the user sees, so very little wastes resources. There are many examples of apps already doing this for both iOS, Android and web.
Cheers.
Réponse de roland684
le 3 juin 2014 à 08h08
How about an option to DECREASE the page size? As you mention you yourself only show 10 results per page. And in a situation where there are 15 items per page, you'd need to do 2 request to get all the results for page 2. Re-paginating paginates results, for only 2% of the users, is cumbersome.
I currently only want the first or first 5 results and have written a piece of code to discard the other results. Transferring and parsing that extra 1.5 kB is no big deal, but it doesn't feel efficient.
Réponse de Travis Bell
le 3 juin 2014 à 09h55
We have no plans to allow changing the page size.
Réponse de scerrutti
le 22 juillet 2015 à 05h02
Hi. This would be a great improvement. I don't want to get 20 related movies, 4 is enough to me. Faster and lighter request, less code for us to limit the request manually. Is it out of roadmap yet? Thank you!
Réponse de Travis Bell
le 22 juillet 2015 à 11h17
Hi scerrutti,
We do not have any plans to support custom page sizes at this time.
Réponse de dieggo
le 27 juillet 2017 à 15h19
Hi I think that should be a dynamic parameter the number of results you want and with that would solve the problem
Réponse de Travis Bell
le 27 juillet 2017 à 17h50
Hi @dieggo Yes, that would solve it but it's still not something I am worrying about right now.
I recently discussed this in another post and pointed out that a fairly standard page of 20 items sent over the wire with gzip is only 5.7KB. I appreciate the desire to get small optimizations like this but 5.7KB is pretty small.
Réponse de gdeleon101
le 3 mai 2018 à 16h06
Travis,
Where can I find out how to query more results as the user scrolls the page (iOS ) to create the "infinite scrolling"?
Réponse de Travis Bell
le 3 mai 2018 à 16h23
Hi @gdeleon101,
You can use the
page
parameter to scroll through pages.Etc...
Réponse de gdeleon101
le 22 novembre 2019 à 10h57
Travis,
I get the string you are adding to the call, but I'm not sure how to call that in swift. Do I need to call another function? What I'm currently doing is loading a collectionView using this function: