The 1.5.5 pre-release that was just announced today includes:
We have increased the URLFetch maximum deadline from 10 seconds to
60 seconds.
So I am thinking: I posted this topic four days ago. I gave it two days to
see somebody from Google reply that they will do it or that they will never
of instance time.
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of PK
Sent: Tuesday, October 04, 2011 2:11 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: urlfetch maximum interactive timeout why
10 seconds and not 20
.
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of PK
Sent: Tuesday, October 04, 2011 2:11 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: urlfetch maximum interactive timeout why
10 seconds and not 20
For PayPal integration on App Engine, you need to ensure that you
split your PreAuth/Capture phases (i.e., never do a straight up
Purchase), and you have to implement their IPN mechanism to know the
true state of things. A PreAuth takes longer than a Capture, but if a
PreAuth times out, the
My integration is with a new service
called Dwolla. It was particularly
embarrassing because the sandbox
always takes less than 10 seconds so
the issues arose only with real
customers in production.
Yesterday night, I implemented the
urlfetch part using a task so
now I should be good for up to
10
If you are referring to Paypal url calls made under their test
environment -- these ran much more slowly (variably) for me vs.
production. Overall, GAE is difficult to ensure PP completion. I'd
made several comments a long time ago (b/4 pull queues instances)
for a single, high-performance TQ to
it's annoying isn't it. could you catch the error and query the api again to
check payment status?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
Hi PK,
We build a 500 qps website that do handle the payments from two payment
gateways: PayPal and PagSeguro (from Brazil). Both suffer for those
problems, and we only was able to solve this by using Task Queues. What we
do is to proccess using this workflow:
1. User is redirected to
Not sure what your are using for the urlfetch method, but it does have
a deadline parameter. Some syntax examples:
urlfetch.create_rpc(deadline=20)
urlfetch.fetch('http://'% domain, method=urlfetch.GET, deadline=20)
--
You received this message because you are subscribed to the Google
