best way i found is to use any entity and +1 rule. and back link using HTTP REFERER (not accurate but reliable in most conditions..)
On Nov 19, 9:38 pm, "Abel Rodriguez" <[EMAIL PROTECTED]> wrote: > I am currently doing a detailed study on how to optimize my > application to be scalable. > > I have thoroughly studied the lectures delivered by the engineers at > google, and my opinion: fantastic > > In this case, my question comes from the presentation > > Buildding Scalable Web Applications with Google App Engine whose > rapporteur was Brett Slatkin > > In it, in the section "Building a Blog: Paging ", using the attribute > index, get to paginate infinite elements, using the index as a guide > for the next entry > > Now, suppose you delete an entity, the attribute index would not be > consecutive. taking into account that, any idea howto implement > paging that supports not only next and previous, but also, goto "n" > page number.? > > thanks in advance, > > Abel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
