Hi,
On Nov 28, 11:26 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > and terminated on response. In attempt to overcome this limitation, I > downloaded the Google App Engine development env. and spawned a > thread. Surprisingly, the result is the same: the "main thread", which > produces the http response, waits for the child thread to terminate > before it sends the response. I do not know why it is so. Peahaps, all > the request threads "live" in the same transaction, which commits only > when they all terminate. Also don't forget that the Google App Engine SDK is meant to simulate executing on the GAE production server. At the time of this writing, the GAE production server does *not* support daemon threads. It only supports short-lived threads that receive a request and return an immediate response. Basically any other decent hosting service *will* support daemon threads. GAE is the exception. e.g. I used to use a 100 Megs Web Hosting host to run TWiki, and I was able to run cron jobs (a kind of daemon process) just fine on their server. Of course, you would have to pay to use 100 Megs's service, while http://schedulerservice.appspot.com/ is free at the moment, last I checked. Sincerely, --Jonathan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
