Using the TaskQueue for asynchronous URLFetch is not a good solution. It has severe limitations. It can have a maximum of 20 simultaneous calls (no matter how many users you have). And each of those calls eats into your "simultaneous dynamic request limit" of 30.
On Jan 19, 3:39 am, John Patterson <[email protected]> wrote: > The task queue can allow you to run synchronous operations in > parallel. Perhaps you could solve your problem by firing off many > tasks each which fetches a url stores the result in memcache and > increments a counter. From your original request keep polling the > value of that counter until all tasks are complete and collect the > results. > > On 19 Jan 2010, at 05:24, devadvocate wrote: > > > Hi all, > > > I'm just checking in to see if Async Http Requests For Java are a > > priority and may be released anytime soon. If not I'll have to > > rewrite most of my app in python or use rackspace cloud hosting :-( > > > Thanks, > > David > > -- > > You received this message because you are subscribed to the Google > > Groups "Google App Engine for Java" 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 > > athttp://groups.google.com/group/google-appengine-java?hl=en > > .
-- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
