I see. So in the event that I had to remove objects from the first 20 and fill it in with results from 20 - 40, I would return that number so the client would know to request from say,
23 - 43 (in case I had to add 3 to fill it up to 20 results). That seems like it could work, I'll give that a shot. Thanks On Jun 19, 8:36 pm, Maaartin-1 <grajc...@seznam.cz> wrote: > On 10-06-19 20:11, coltsith wrote:> Nick, thanks for responding. > > > I've thought about doing that but then run into another issue: > > > If I request 20 objects and the first 20 were created by the user, the > > server will return an empty list. > > > Internally I suppose I could load like 1000 objects to ensure that > > I'll get the necessary 20, but that brings up issues with paging. > > Loading 1000 objects makes sense under the following conditions > - either the user created the vast majority of the objects > - or you have no chance to start another query in case the first one > returned too few objects not created by the user > Otherwise, I'd fetch 40 results (or about). > > > For example: > > > user requests objects 1 - 20, first 20 objects are actually created by > > user. server returns objects 21 - 40 > > client increments page index to 20. > > user hits "More" and requests objects 21 - 40. server returns the same > > objects as the initial request. > > Is there any reason to fetch with offset 20 instead of the proper one? > When you can filter out some results, you can add their number to the > offset as well, can't you? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
