You could have the tasks from the 'producer' app use URL Fetch to call service endpoints in the consumer. The endpoints could either insert tasks or do the work.
If you're just trying to keep codebases isolated and separate, you could use different versions within the same app. You can specify which version of an app task in a given queue should run on using the target parameter. Either way, you might be making a design that is much more complex than needed. If you don't have a really good reason for doing this I would take Vlad's suggestion and use a single app. Robert On Mon, Apr 25, 2011 at 06:58, vlad <[email protected]> wrote: > Sharing a TaskQueue or any other resources between apps is not possible by > design. > > Just have your Producer and Consumer as different urls within a single app. > > -- > 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.
