That is correct, all tasks get the same host header as the request that created them. This means that if you access the url http://0.backend-name.app-id.appspot.com/ and it inserts a task, the task will execute against instance 0 of 'backend-name'.
If you access the url http://backend-name.app-id.appspot.com/ and it inserts a task, the task will execute against any instance of 'backend-name'. On 14 May 2011 15:31, Aaron <[email protected]> wrote: > A follow up to this question is if we can use the new pipeline API > with backends. If we start a pipeline in a backend, will all future > pipeline tasks be processed by the backend? > > On May 14, 2:41 pm, Aaron <[email protected]> wrote: >> Hi, >> >> The way my application is set up involves deferring a lot of long- >> running tasks, which I now would like to move to a backend. Is it >> possible to defer a task so that it is processed in a backend? Or, do >> I have to create handlers for every deferred task in order to take >> advantage of this feature? >> >> Best, >> Aaron >> >> P.S. Thanks so much for the hard work! The new features are very >> exciting :). > > -- > 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.
