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 minutes. PK On Oct 1, 2011, at 6:56 AM, Jason Collins <jason.a.coll...@gmail.com> wrote: > 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 consequences are less: on your IPN, if you get > a PreAuth transaction that you don't know about (i.e., because it > timed out), simply Void it. If your PreAuth succeeds, you can issue a > Capture which is typically quite quick. > > It's a pain given the short(ish) url fetch timeout (or, if you look at > it another way, the long time PayPal takes to process cards > sometimes), but it can be done. > > j > > On Sep 30, 8:51 am, stevep <prosse...@gmail.com> wrote: >> 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 address key weaknesses. Note: My >> only frame of reference is PP's digital goods purchase process. >> >> HTH, >> stevep >> >> On Sep 29, 1:40 am, PK <p...@gae123.com> wrote: >> >> >> >> >> >> >> >>> I have integrated my site with a cool online payments service. They provide >>> an API for online payments that I access from the server side using the >>> urlfetch() API. Unfortunately, once in a while their service takes a little >>> bit more than 10 seconds to respond on the pay API, so the payment goes >>> through but my code gets a timeout and reports an error to the user which is >>> very frustrating. >> >>> I am trying to get the online payments vendor to improve their response >>> times but I was wondering why did you pick 10 instead of 20 seconds for the >>> urlfetch maximum timeout. In 30 seconds there is enough time to get in, do a >>> 20 second urlfetch and return in worst case. >> >>> Thanks, >>> PK >> >>> PS Yes I have thought of doing the urlfetch from a task but the code gets >>> pretty complicated pretty fast. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
