> Put this as vote to provide multithreaded dev server. I promise I > won't start my own hosting farm.
A multi-threaded dev server only makes sense for thread-safe applications. Currently the app engine platform doesn't expose anything that can be used to make thread-safe applications. Since the production version carefully hides any thread-like behavior, this is unlikely to change. On Apr 1, 6:06 am, Mark Wolgemuth <[email protected]> wrote: > The dev server appears (obviously) to be single threaded, as is the > django dev server. > > The presents a problem if you want to post to your own server > location. An example would be posting to the url provided by > create_login_url, which in dev answers at the same location as your > app. The server gets stuck waiting for the parent request to finish > before allowing the urlfetch to execute, times out and fails. > > In production these urls would be answered by different servers, so > should work. But to develop I have to hack it so I have 2 separate dev > instances running. > > There are other circumstances (health checks, etc) where you would > conceivably want to POST to yourself. Does anyone know if this is > allowed in production? I assume so. > > Put this as vote to provide multithreaded dev server. I promise I > won't start my own hosting farm. > > --Mark --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
