I'm *pretty sure* it just means that the task inherits the namespace (for the purposes of data store and memcache access) from the request that inserted it into the queue-- it won't create parallel queues.
On Fri, Sep 10, 2010 at 7:14 PM, Shimon Rura <shimonr...@gmail.com> wrote: > I've been learning about the namespacing system and am wondering about > its behavior with task queues. I'm not sure about the effect of > enqueuing a task under a particular namespace. The docs state that > when the task request runs, it will use the same namespace for queries > to the datastore, memcache, and other namespace-enabled APIs. But is > that it, or are there actually effectively separate task queues for > different namespaces? > > Here's a more specific question. If I have a queue called "foo" that > executes 1 task per minute, and I put two tasks into it under > different namespaces, will it execute them at the same time? Or will > it subject them to the queue's overall rate policy, executing the > first ASAP but then waiting a minute to launch the second? > > Thanks, > Shimon Rura > > -- > 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<google-appengine%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ross M Karchner http://eventgrinder.com -- 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.
