Exploring Google AppEngine, Part 2

In my first experiment with Google's AppEngine, I dove straight in and started using CherryPy for development. This worked pretty well at first, but I eventually hit some issues due to lack of threading within AppEngine.

At that point, I decided to step back a bit and take a fresh look with a pure-WSGI approach. I had never used WSGI directly, so this was an interesting experiment. I definitely like the simplicity of pure-WSGI, but the question will be how much custom code I have to write versus using a prebuilt framework. (Don't get me wrong, I expect to return to CherryPy later, but I want to experiment at the lower level for now.)

You can follow the work in progress at boodebr.appspot.com
Written in WikklyText.

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

WSGI

You should definitely take a look (and more) at Werkzeug (http://werkzeug.pocoo.org/), a clean and slim WSGI library. Then you can add components (template engine, ORM etc.) to your app's stack as you like.

threading

what were the threading issues you ran into?

Threading issue

Here is more about the threading issue: cherrypy list

I have a workaround that seems to work, so hopefully I will be adding that to boodebr.appspot.com soon.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.