Dear voltron; >From my experience FCGI yeilds better result While Reverse Proxy is a lot easier to deploy.
Main advantage of Reverse proxy is , suppose you do not have mod_wsgi on Apache , you can easily make a configuration directive for reverse proxying web2py service running behind. The main disadvantage is You have to run two Long Running Processes on the server , One for apache , One for CherryPy , so two CGI servers are running at once , i will take more resources. While FastCGI connects to sock listening by web2py_fcgi.py , it do not need to keep two long running processes. which is more lighter then proxying But , one problem is Many host providers do not have mod_wsgi by default . So thats my .02$ for now. I have not make any benchmarks . On Mon, Jan 19, 2009 at 7:06 PM, voltron <[email protected]> wrote: > > Does anyone have any experince with deploying web2py using FCGI or via > Apache revers proxy? Which uses up more memory? > > > Thanks > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
