I should also add that, while the DateTimeProperty seems like a good idea for paging, keep in mind that it is not necessarily unique. This is due to the fact that your app runs on a distributed system, and clock times on the machines are not exactly synchronized (there have been several threads on this group discussing clock timing, if you'd like further information).
-Marzia On Thu, Oct 30, 2008 at 10:24 AM, Marzia Niccolai <[EMAIL PROTECTED]> wrote: > Hi, > > I suggest the video 'Building Scalable Web Applications' by Brett Slatkin. > It deals with how to implement an index for paging for applications with > high and low volume writes. The right strategy depends on what you expect > the write volume to be for your app: > http://sites.google.com/site/io/building-scalable-web-applications-with-google-app-engine > > -Marzia > > > On Thu, Oct 30, 2008 at 6:59 AM, gops <[EMAIL PROTECTED]> wrote: > >> >> another idea - which might not be much reliable - is to use >> HTTP_REFERER for previous link as it is very likely that nobody is >> going to go directly to next page without >> previous page. :D wat say ? >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
