I'm just giving a not-well-thought suggestion, but I'd rather use memcache for this.
I guess something like using a time-dependent code as the key (i.e. a counter which increments every 30 seconds) and a list of user ids as the value, and simply doing a get() on the cache for the current counter value would work. I don't know how this could scale, due to concurrent updates, but I definitely think Memcache is the way to go, not datastore. Regards Lorenzo On Jun 23, 5:45 am, Ryan <ryeterr...@gmail.com> wrote: > Each of my users is polling the server every few seconds. I need to > keep a list of the users that have polled in the last 30 seconds handy > for a task I have queued to run every few seconds. > > The obvious way I see to do it is to update a datastore entry every > time the user polls, and query the entries that have a timestamp > within the last N seconds within my task queue. I can't imagine this > scaling well. > > Any recommendations? > > Thanks. -- 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.
