Pylons for FAPWS2

There was a question on my blog about FAPWS2 and Pylons. I was able to post a comment about it in the entry however I was trouble because I could not get a patch to the maintainer of FAPWS2 however William published FAPWS2 on github (http://github.com/william-os4y/fapws2/tree/master). It has then motivated me to create an account and contribute my personal contributions to the project. Which you can find http://github.com/lateefj/fapws2/tree/master. At the moment I have been able to just add a Pylons example on configuration. Mainly there is a run.py and development.ini that where modified to support Pylons. Last time I benchmarked it the performance was around 30% increase.
Next commit is I want to integrate my Frisky contributions into FAPWS2 this would help to see if I can get other to find out if they are getting the same performance with the caching utilities, static folder configuration (WSGI application are slow at serving static files). Just sent off email to make sure all the features I am proposing are sane. Can't wait to start hacking on it!

Cython is way cool, and makes optimizing Python faster

As I have previously mentioned I started the C module for the FAPWS2 web server. That was not to bad however the scope of the C is very small. FAPWS2 goal is to be the fastest WSGI server then there are a lot of things that could be optimized using Cython. Trying to move Python to C would be a very long and slow task with a lot of potential land (memory leak) mines. However to move the Python to Cython would be a much faster and more stable direction after a good amount of profiling.

On a day to day basis I don't think about the early binding performance hit of Python because Python is fast enough. However there are a number of finite things that because of the volume of calls could be a bottlneck for high performance code. I look forward to experimenting with Cython to make FAPWS2 faster.