> It should be fairly straightforward to handle this polling in
> Javascript, eliminating the infinite redirect loop and allowing for
> the possibility of giving status readouts for the user :)
That sounds promising. I very familiar with Java, but have just
started playing with javascript recentl
On Jun 16, 3:15 pm, J Keller wrote:
> Thank you Scott - that redirect trick worked great.
>
> After processing a subset of the data, I simply redirect back to my
> service. Each time it caches more of the data, until the job is
> complete. Sometimes this can cause the browser to give up and r
Thank you Scott - that redirect trick worked great.
After processing a subset of the data, I simply redirect back to my
service. Each time it caches more of the data, until the job is
complete. Sometimes this can cause the browser to give up and report
an 'infinite redirect loop', but it usuall
invoking URLs.
-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appeng...@googlegroups.com] On Behalf Of J Keller
Sent: Wednesday, June 03, 2009 4:09 PM
To: Google App Engine
Subject: [google-appengine] Re: DeadlineExceededException - how to avoid?
That might
You may want to look in to the remote API if you want long-running
processes without waiting for them to be added; you'll have to provide
your own hardware and use the bandwidth to send your data back and
forth, but you can do whatever processing you want and you can do it
now.
On Jun 3, 5:08 pm,
That might help some, but according to the docs:
A cron job will invoke a URL at a given time of day. A URL invoked
by cron is subject to the same limits and quotas as a normal HTTP
request, including the request time limit.
Unfortuantely, I don't think I can reasonably break my task down in
On Jun 3, 10:46 am, fel wrote:
> yeah but what if it is a banking app that needs to do all sorts of
> complex transactional processing?
Any bank that would trust the Datastore, with its inability to do
transactions across entity groups, to handle its data is probably run
about as well as, well
2009 9:47 AM
To: Google App Engine
Subject: [google-appengine] Re: DeadlineExceededException - how to avoid?
yeah but what if it is a banking app that needs to do all sorts of
complex transactional processing?
On Jun 3, 9:09 am, Wooble wrote:
> On Jun 3, 9:51 am, J Keller wrote:
>
&g
yeah but what if it is a banking app that needs to do all sorts of
complex transactional processing?
On Jun 3, 9:09 am, Wooble wrote:
> On Jun 3, 9:51 am, J Keller wrote:
>
> > Ouch. So does this mean I can't use the GAE to do any operation
> > that's going to take longer than 30 seconds?
>
>
On Jun 3, 9:51 am, J Keller wrote:
> Ouch. So does this mean I can't use the GAE to do any operation
> that's going to take longer than 30 seconds?
>
> Surely that's not the case - that would change it from being a very
> useful tool, to one which is useless (for me, anyway).
>
> I hope I'm mi
Ouch. So does this mean I can't use the GAE to do any operation
that's going to take longer than 30 seconds?
Surely that's not the case - that would change it from being a very
useful tool, to one which is useless (for me, anyway).
I hope I'm missing something...
--~--~-~--~~---
On Jun 2, 5:20 pm, J Keller wrote:
> If not, I suppose I could spin off multiple threads on the server
> side, and hope they all finish in time.
No, you can't. It's impossible to create new threads.
--~--~-~--~~~---~--~~
You received this message because you ar
Okay, thank you Nick.
Is there any way I can somehow continue processing, after returning a
response to the user?
If not, I suppose I could spin off multiple threads on the server
side, and hope they all finish in time.
Thanks again.
-J
--~--~-~--~~~---~--~~
Yo
Hi,
You can catch the first DeadlineExceededException, after which you have a
short time (less than a second) to wrap up your request and return a
response to the user. If you fail to do so, a second, uncatchable exception
is thrown to terminate your script.
-Nick Johnson
On Tue, Jun 2, 2009 at
14 matches
Mail list logo
