I'm reading the asynchronous URL request API, and I'm a bit confused about it. The documentation mentions that callbacks aren't called when the request finishes, rather you have to call them explicitly. To me, this would seem to defeat the point of an asynchronous request - your application will still be locked up while the first wait() is called. Of course, any other requests could still continue to be retrieved in the background, but if the first request is the last to be retrieved, the application will be blocked when it could otherwise be processing the data from a request that had been received.
My application involves pulling data from several outside sources at a relatively frequent interval, which thus far has been consuming the vast majority of my CPU usage. I'd hoped asynchronous requests would cut down on this a little, but at least by my understanding the performance gain will be minimal. Can anyone enlighten me on this? -- 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.
