c2c-oerpscenario team mailing list archive

["Xavier \(Open ERP\)" <540255@xxxxxxxxxxxxxxxxxx>]

However, note that Maximilian's warning is correct: I believe there are
still issues with the file-based session storage in 6.0, so if you're
using a process-based concurrent wsgi server you'll have to use sticky
sessions.

-- 
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