Your application probably isn't written to be multi-threaded and any
effort to make it so is wasted because it won't be executed as multi-
threaded in production.
You could get around application threading issues by forking but then
you'll discover that the dev server's datastore is a pile of
Perhaps I didn't explain my problem clearly. This problem applies
only to the development server (dev_appserver.py or SDK). The problem
is it is single threaded, so when multiple requests arrived at the
same time, they have to be served serially (one after the other), so
one of the request got
Khai, I recently posted a bit on my blog about this:
http://blog.chilly.ca/?p=238
You'll probably be pretty hard-pressed to run it on anything but the
dev_appserver, and it's not very likely that you'll get it working
multi-threaded. Sorry :(
On Apr 6, 5:59 pm, Khai khaitd...@gmail.com
That's a very bad idea: dev_appserver is not secure, is snail slow if you
add more than a couple of thousand entities in it and it is uncertain if it
can share a datastore across multiple instances.
Why do you want to do this? What is wrong with hosting on GAE?
On Sat, Apr 4, 2009 at 11:04 PM,
