rote:
> Hi,
>
>
>
>
>
>
>
>
>
> On Fri, Apr 29, 2011 at 8:36 PM, footy wrote:
> > Thanks for the reply Ravi,
>
> > No3. The worry is not scaling. I know GAE will do it for me.
> > What I was trying to say is that the level of scaling required for
> > Producer
ull
> requirments,designs,constraints etc but i can say your 3rd reason is kind of
> invalid as you dont have to worry about scaling much...GAE will do it for
> your self.
>
>
>
>
>
>
>
> On Fri, Apr 29, 2011 at 10:01 AM, footy wrote:
> > Thanks Nick and St
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
Thanks guys for some info on task queues..
I will try and outline what I am trying to do.
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
Consumer: Consumes these photos and processe
I would like to create two different apps a Producer App and Consumer
App.
Is it possible to use the Task Queue to share jobs between the two
apps?
If so could anyone point me to caveats around that?
If not , can someone tell me how to achieve what I am trying to do?
Thanks
--
You received thi
t; ..:
>
>
>
> On Fri, Feb 25, 2011 at 5:53 PM, footy wrote:
> > I was wondering what is the best to manage a new release on App Engine.
> > Say for example we have a live version (default) as 1.0.0 and we make
> > changes to our code and deploy to a new version as 1.0
directly.
>
> Change the default version.
>
> In my experience, that pattern avoids the server error. It still takes
> several seconds for all servers to start showing the new version, but you
> don't get the 500's.
>
> On Feb 25, 2011, at 11:53 AM, footy wrote
Oops my bad.
Ours is a Java application.
Also, I am new to GAE.
So how do you generate a load against the new version?
The error page goes as follows
"Error: Server Error
The server encountered an error and could not complete your request.
If the problem persists, please report your problem
I was wondering what is the best to manage a new release on App Engine.
Say for example we have a live version (default) as 1.0.0 and we make
changes to our code and deploy to a new version as 1.0.1.
When I change the default from 1.0.0 to 1.0.1 it takes GAE to propogate
changes across the clust
