Thanks Nick and Steve for your answers.

I wasn't planning on storing data in the queue, but just a job message
with a payload giving enough information to the Consumer ( photo
processor ) for further
processing of the images.

Also, by consumer I don' mean the user itself, but as a design pattern
of Produce - Consumer. The images are produced ( uploaded ) by the
producer.

My main query was regarding sharing the task queue between two apps.

App1 = Producer - produces (uploads) images
App2 = Consumer - consumers ( processes ) images

Steps:
1. App1 finishes the upload of images to datastore.
2. App1 creates a Job message in the task queue called Job1
3. App2 picks Job1 message from the task queue
4. App2 finds the image specified in the payload of Job1 from
datastore
5. App2 does processing on the image and stores it back in the
datastore
6. App2 notifies App1 that the processing is finished.

Reasons for doing this
- separate, isolated code base
- can be managed separately
- can easily deal with the different level of scaling requirement for
both App1 and App2

Would it be possible?

On Apr 29, 8:08 am, "Nick Johnson (Google)" <[email protected]>
wrote:
> On Fri, Apr 29, 2011 at 4:12 PM, stevep <[email protected]> wrote:
> > You wrote:
>
> > > Producer: Produces photos. These are uploaded by the user.
> > > Once the upload is done, I would like to put up a task in the queue,
> > > to be ready for further processing
>
> > Keep in mind that data payloads sent to a taskqueue are quite
> > constrained re: size.
>
> > I tried sending a 600x400 pixel jpeg image, and it would error out.
> > Nick, though, infers there is a workable means.
>
> Yes - simply store the original image to the datastore. If he's dealing with
> large images, they were probably already uploaded to blobstore, in which
> case he needs merely pass the blobkey to the task.
>
> -Nick Johnson
>
>
>
>
>
>
>
>
>
> > TQs in my experience are great in concept, but oft lack for
> > applicability for real-world problems.
>
> > Despite that, I use them extensively.
>
> > Best of luck,
> > stevep
>
> > --
> > 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.
>
> --
> Nick Johnson, Developer Programs Engineer, App Engine

-- 
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.

Reply via email to