Hi!
I did some testing. I performed an asynchronous urlfetch without a
callback parameter nor did I call wait() or get_result() before I
returned the response to the user.
The analytics is being logged properly, so that's great. But I'm
getting the following warning in my logs.
Found 1 RPC
Thanks!
Albert
On Aug 9, 11:05 pm, Nick Johnson (Google) nick.john...@google.com
wrote:
Hi Albert,
On Sun, Aug 8, 2010 at 12:46 PM, Albert albertpa...@gmail.com wrote:
Thanks for the vid link! I learned some other good stuff from there.
However, I don't think my question was clearly
Hi
On Aug 8, 7:46 pm, Albert albertpa...@gmail.com wrote:
Thanks for the vid link! I learned some other good stuff from there.
However, I don't think my question was clearly answered.
I hope I get a clear response from the AppEngine Team on this one.
When I start an asynchronous urlfetch,
Thanks!
I will do some tests. I'll posts my results here.
Enjoy!
Albert
On Aug 8, 11:24 pm, Tim Hoffman zutes...@gmail.com wrote:
Hi
On Aug 8, 7:46 pm, Albert albertpa...@gmail.com wrote:
Thanks for the vid link! I learned some other good stuff from there.
However, I don't think
Thanks for the reply.
That's a good solution to return a response ASAP.
But, I'm guessing that adding the urlfetch to a task would consume
extra CPU ms time.
I want a solution that returns the response ASAP and, at the same
time, consumes the least CPU resources.
I'm assuming that the docs
