Yeah, exactly. There are several other variations on the same theme too. If you were to use long-running tasks or cron-jobs for this you might need some type of locks or guards in case two run at the same time. A backend should simplify the process quite a bit since a process can run for a very long time (24 hours) and you can crank up the memory; the downside is that backends extremely expensive and they won't be able to scale as wide as a task-based method.
Robert 2011/8/17 Sébastien Tromp <[email protected]>: > If I understand correctly, in both cases I need to retrieve all the objects > that are in my cache, extract the ones that need to be processed "soon", and > process them. > Using a backend or a cron changes the environment in which this process > executes, but not the process itself. And in this case, a backend seems > indeed more suited to this. > Is that what you had in mind? > -- > Sébastien Tromp > > On Wed, Aug 17, 2011 at 10:05 PM, Robert Kluin <[email protected]> > wrote: >> >> I was actually thinking more about firing a long-running cron every 5 >> minutes to do what ever processing you need. However, I still think >> backends are probably a better choice. > > -- > 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. > -- 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.
