Hello,
If you have control over the remote site, you can push a request to the
remote site to tell it to send an updated content via post to a service
that is deployed on GAE.
For Example:
GAE App -> sends request to a remote site that is ready to receive the
new content
External Site -> sends "OK" to the GAE App to indicate that request was
accepted and date will be available shortly
External Site -> posts content to the GAE App (here we have 30 sec limit)
GAE App -> updates the content and sends some response to the external
site to indicate that the content was saved successfully
I know, it's not a perfect solution, but it works.
Regards,
Miroslav
On 06/29/2010 04:04 AM, Peter Liu wrote:
I am having issue fetching a html from user's specified url, which
very often takes 10+ seconds (maybe it's outside US, maybe it's a cold
start, maybe it's just plain slow).
I am retrying the request every hour, but quite often it will fail
again. However, if another request is made immediately, it will likely
succeed.
Retrying actually use more resources in the end.
Will this limit ever be lifted or relaxed?
There seems to be no way around it if the page do take 11 seconds to
load.
Also, I want to point out that calling URLs served by other app on app
engine can cause timeout (if it's a cold start request). This makes it
hard for our own apps to communicate with each other (since different
app can't share same datastore).
Maybe an asynchronous URL fetch service will be nice (with longer
timeout). The service can be similar to the queue service, except that
it takes a fetch-url and the fetched data is served to the callback-
url.
Anyone facing this problem and have a solution?
Thanks.
--
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.
