Hi Michael, Thanks for your reply.
I'm afraid I can't point to a specific URL, this has been happening seemingly at random. As I said, if I reload the same URL immidiately afterwards, 'entry' is properly populated. Regarding the caveat: yes I am experiencing that as well. This is quite the problem, we are on a device with very limited memory so I am not able to cache results at all. It seems caching would be the preferred way of using the API. However, it does seem like Google is caching the result feeds a lot.. which causes even more strange behaviors in the app when switching between pages =) So based on the comment in the API reference, the following is true? "To make the community search feed usable in any app, caching results on the application side is a must." Thanks, Mattias On 16 mar, 18:01, Michael Erickson <[email protected]> wrote: > You are correct in the use of start-index and max-results. > > Can you post one of the feed URLs that is giving you trouble? My > tests here have returned the correct number of results for several > different queries. > > This can be used for pagination, but with the caveat indicated in the > discussion of query parameters: > > "Note that this isn't a general cursoring mechanism. If you first send > a query with ?start-index=1&max-results=10 and then send another query > with ?start-index=11&max-results=10, the service cannot guarantee that > the results are equivalent to ?start-index=1&max-results=20, because > insertions and deletions could have taken place in between the two > queries." > > fromhttp://code.google.com/apis/gdata/docs/2.0/reference.html#start-index > > Thank you, > -Mike > > On Mar 15, 10:33 am, Mattias Lindvall > > > > > > > > <[email protected]> wrote: > > Hi, > > > Sometimes when using the community search feed /feed/api/all, I have > > been experiencing the following: > > > I request using an arbitrary start-index (> 1), and max-results set to > > 8. The response has openSearch$itemsPerPage set to 8, but there are > > only 7 entries in 'entry'! (0-6 instead of the expected 0-7.) > > > If i re-run the same request again, 'entry' is properly populated. > > > I know there are more results available (searching for something > > arbitrary like 'adg' gives me tens of thousands of results). > > > Am I missing something about how the pagination works in Picasa? As > > far as I can tell from the API spec, I should be able to use any > > combination of arbitrary values on start-index and max-results, > > correct? > > > Thanks, > > > Mattias Lindvall > > Application Manager > > Accedo Broadband AB -- You received this message because you are subscribed to the Google Groups "Google Picasa Web Albums API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-picasa-data-api?hl=en.
