| ||
Sat 2024-12-21
Fri 2024-12-20
Thu 2024-12-19
Wed 2024-12-18
hydroxychloroquine fraud withdrawn Tue 2024-12-17
Sun 2024-12-15
Sat 2024-12-14
Fri 2024-12-13
Thu 2024-12-12
Tue 2024-12-10
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
I'm working on a little webapp project. Usually I just use plain old
Python CGI scripts for these things but this time I actually care
about performance a bit so I did some delving into the modern world of
Python webapps. Things are a lot better than they used to be. WSGI is the
standard Servlet API, web.py (small) and Django (big) are good app
frameworks, and Zope is mercifully
sliding to retirement. But I'm stubborn and want to do things my own
way, just use FastCGI to avoid invocation overhead.
Turns out it's easy on a Debian system. Install the packages python-flup and libapache2-mod-fastcgi. Then write a python2.4 program like this:
#!/usr/bin/python2.4
import flup.server.fcgi g = 0 def app(environ, start_response): global g status = '200 OK' response_headers = [('Content-type','text/plain')] start_response(status, response_headers) g += 1 return ['Hello world! %d\n' % g] if __name__ == '__main__': from flup.server.fcgi import WSGIServer WSGIServer(app).run() The one badness is that modifying your Python code won't force a code reload, which sucks for development. If you name your program "foo.cgi" Apache will invoke it as normal CGI and Flup supports that too, so that's what I'll do for now. Even if it behaves differently. |
|
