We use mod_python with paste.modpython and it works reasonably well - but it's an extra level of configuration (apache stuff) so I'd recommend against it. Only thing about proxying is that if you're on a multi-core machine and want to exploit all cores, Python threading kinda blows. So if you're using the default multi-threaded paster and your app is in any way CPU intense, you're going to see performance suffer.
Alec On 8/23/07, Andrew Smart <[EMAIL PROTECTED]> wrote: > > Hi Steve, > > Not so easy. You have three options (my experience): > - cgi: very slow > - fastcgi / mod_python: apache module; possible but quite difficult to > setup > > -> depends strongly on what your provider gives as options > -> depends also if you have python2.4 pre-installed on your environment > (if not, even more difficult) > - running the paste application as http server and use apache as proxy > > After fiddling heavily with mod_python I finally gave up and did choose > the > proxy approach which was surprinsingly easy. But you'll need some > priviliges > on the server (shell access, the right to start processes, access to > apache, > mod_proxy etc). > > I know that others did succeed with mod_python or fastcgi, so you may take > this approach. You'll find docu about this also in the pylons > documentation. > > Just my 2cents, > Andrew > > > _______________________________________________ > Paste-users mailing list > [email protected] > http://webwareforpython.org/cgi-bin/mailman/listinfo/paste-users >
_______________________________________________ Paste-users mailing list [email protected] http://webwareforpython.org/cgi-bin/mailman/listinfo/paste-users
