The autogenerated ID is not guaranteed to be sequential, but it is guaranteed to be unique. It seems fairly unlikely that the times would be out of sync, but you can use Memcache's INCR on values. This is atomic and returns the next higher integer value.
On Fri, Mar 26, 2010 at 1:45 AM, jbdhl <[email protected]> wrote: > I know that the app engine servers are synchronized with NTP so that > their clocks should be almost perfectly synchronized. Should. But can > I rely on that? Are there any mechanisms that decouples a node if its > clock gets e.g. more than N seconds out of sync the rest (or some > master node)? If so, what is the number N? > > In my app I need to receive objects that has changed since last call > to the server, and normally I would have used some sequence/serial > datatype for that. But such a datatype isn't effective in a > distributed environment so I'll try to "hack" the same functionality > using a Date instead, and then just "handle it" if the client receives > a few already received objects when polling the server. This may > happen if the server clocks aren't perfectly in sync. > > -- > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- 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.
