Thanks for this. I may give it a try (after just rewriting my code to go back to using the handler).
Important question: the central value proposition of using deferred (from the docs) is below. Can anyone confirm that passing a function and related data to one's queue is going to not hit the limit. I don't want to code all this up just to see another log error saying task queue item sizes are limited. The deferred process seems to add marginal ease of development on my side vs. what I would guess is more overhead on the task queue side. So why would getting a task queue item set via a deferred function call be unlimited by Google vs. the less complex (I'm guessing here) direct task queue function call? [GAE design optimization: "an enigma, wrapped in a mystery..."] >From Google's docs: "The deferred library will package up your function call and its arguments, and add it to the task queue." On Feb 11, 4:47 am, djidjadji <[email protected]> wrote: > Have a look at the deferred API in the SDK. No limit on the payload of > a task, it is stored temporarily in the datastore. -- 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.
