I have now solved it by using sequence counters and instead of presenting 'N seconds ago' to the users it now says 'seconds ago'. It should work as long as the time difference between servers is less than one minute.
On Jan 13, 9:17 pm, Anders <i...@blabline.com> wrote: > Using a global sequence number ensures correct ordering of records but > not correct ordering of timestamps. If in a chat application the time > is presented to the users with a resolution of seconds, then it may > happen that the timestamps presented will sometimes have incorrect > ordering (such as the newest message being presented as 15 seconds old > while the second newest message is presented as being 7 seconds old). > This is perhaps only a minor problem but anyway. > --~--~---------~--~----~------------~-------~--~----~ 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-appengine@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 -~----------~----~----~----~------~----~------~--~---
