openerp-expert-framework team mailing list archive
-
openerp-expert-framework team
-
Mailing list archive
-
Message #00533
Re: Webclient 6.1 should work in socket and also in mod python
On 2011-04-29, at 09:39 , Nicolas Bessi wrote:
>
> The webclient 6.1 is now quite on the rails and is really promising.
> Although it seems that the webclient is still based on CherryPy.
> I know it is a convenient way to lauch a HTTP server and it is great for dev.
> But in a professional configuration where webclient pages may be exposed to the world this will not be sufficient enough.
>
> IMHO we should be able to launch at least server in socket mode with a python framework like twisted python
I doubt that will happen. Twisted is an evented server and not something we're planning to support at the moment, as far as I know.
> but also we should be able to launch the server as a mod python for Apache or nginx.
Support for WSGI integration is most definitely planned, although we're not quite sure yet whether it will be done using CherryPy (nb: using CherryPy as a framework does not mandate using it as a web server) or by replacing CherryPy by e.g. Werkzeug. We're currently using very few features of CherryPy, and there's a layer over it to handle the nitty-gritty details of json-rpc exchanges with the javascript client, so that should be pretty easy (basically, we're just using CherryPy to parse request data and handle sessions).
> Such kind of integration will be really important in order to have all static content serve by powerful engine, enable load balancing etc…
Serving static content via cherrypy has always been optional, and mostly for development. That's was already the case in the 6.0 client.
Load balancers were more of an issue as non-memory sessions did not work correctly in the 6.0 client (though you could always use sticky sessions on the load balancer), in the 6.1 prototype we're defaulting to file-based sessions (forcing all structures to be serializable and de-serializable) so that should not be an issue, as long as you can manage your session store correctly (nb: you may still want to use sticky sessions)
References