Hi Dan, On Sat, Oct 17, 2009 at 4:45 PM, Devel63 <[email protected]> wrote:
> > I've been "deferring" tasks by using a callback from the user's > browser that follows up an immediate request with other things I want > to happen in the background as a result of that request (e.g., > preparing for the next probable request, putting memcache items into > DB, etc.). > > Is the new deferred capability suitable for this? Yup! > Is it better or > worse than my approach? I would say it's better - it doesn't require client support, isn't susceptible to client issues (like the client going away before it can execute the second request), and in general can't be interfered with by the client. > What are the downsides? > > Is it subject to the 10K task queue insertions quota (making it > completely unsuitable for this)? > Yes, but if you enable billing you get 100k tasks a day, and if you have a good use-case, we can increase that limit further. -Nick Johnson > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
