Raphaël Valyi, I think there are many design dependencies on the "one stack" current design, even the web client is hard enough to make it wsgi compliant, as Xavier comment above the sessions are an issue, I even try to rewrite the session handler but seems to tricky ...
Using wsgi, will be a killer feature ! as WSGI enables a lot of solutions for horizontal scaling I hope the dev team take this more serious -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to the OpenERP Project Group. https://bugs.launchpad.net/bugs/540255 Title: Use WSGI instead of CherryPy demo server Status in OpenERP Web Client: Fix Released Bug description: openerp-web currently uses the CherryPy demo server. It should use Python's standard for web applications, WSGI, instead. It can be nicely integrated with Apache. openerp/commands.py needs only a few change to be usable as a WSGI application, because CherryPy already supports WSGI. cherrypy.config.update({ 'tools.sessions.storage_type': 'file', 'tools.sessions.storage_path': '/var/lib/openerp-web/sessions', }) setup_server should return the app object. Then you can return it to the WSGI handler instead of starting the cherrypy.engine _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
