Think of ajax request as one thread and use client(browser) and server (app engine) as one system for parsing and not as two systems where you parse only on server side.
Ajax request is now thread/fiber/'what ever' in some way in Chrome and in a few years many browsers will act the same. On Dec 23, 12:17 pm, Chen Harel <[email protected]> wrote: > Hmmm... so what do you suggest I do? > > On Dec 23, 12:53 pm, Alexander Kojevnikov <[email protected]> > wrote: > > > Fromhttp://code.google.com/appengine/docs/python/sandbox.html: > > > An App Engine application cannot spawn a sub-process or thread. A web > > request to an application must be handled in a single process within a > > few seconds. Processes that take a very long time to respond are > > terminated to avoid overloading the web server. > > > On Dec 23, 7:02 pm, Chen Harel <[email protected]> wrote: > > > > Hi, What do you think is the best way to parse many XMLs > > > concurrently... > > > I figured threading may be the case, but after reading some Python > > > articles about it, > > > I've decided to post this message, and get some feedback from the > > > community... > > > > Does someone actually uses threads in Python? > > > How can you get massive parsing going in the server side? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
