gaeutilies has a cron functionality (also dependent on user interaction) also.
http://code.google.com/p/gaeutilities/wiki/Cron On Dec 10, 9:26 am, Ben Nevile <[EMAIL PROTECTED]> wrote: > Hi Dennis - > > I am using an architecture similar to what you describe. Rather than > use a separate server to do the pinging, I use client-side JS to do > this dirty work. You need to have a fairly steady stream of users for > this technique to be reliable. :) > > Ben > > On Dec 9, 9:27 pm, Dennis <[EMAIL PROTECTED]> wrote: > > > I'm architecting my system to workaround the limited write ability in > > each gae request. > > > I'd like to use task queues (as in issue > > 109http://code.google.com/p/googleappengine/issues/detail?id=109), > > but that feature is not implemented yet. > > > I'm thinking about using the following: > > -the initial GAE request accepts the user's request and queues the > > task into Amazon Simple Queue Service (Amazon SQS) using a call to an > > external url. > > -a hosted system (external to GAE) polls the SQS queues. > > -when the hosted system finds a task, it makes API calls into GAE to > > do the actual asynchronous work inside GAE and it's datastore. > > > Just wondering if anyone else has used this type of architecture (or > > thought about it) and what their experience / opinion is. > > > The only post I could find about using Amazon's queues > > is:http://groups.google.com/group/google-appengine/msg/86368530077bc548 > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---