The auth param is an auth proxy/provider. The idea is that an auth proxy
is associated to some HTTP request handler. The handler can then use it
when necessary, depending on the accessed resource.
As of now, it is only used by the webdav module. But really, the caldav
module accesses the proxy directly on the handler.
Currently in web_services, authentication is simply done via
security.check().
bzr revid: vmt@openerp.com-20110925152318-i3jvimumm51e2lu4
- added Microsoft specific header for webdav.
- serve WSGI handlers with werkzeug when available.
- effectively use WSGI instead of netsvc HTTP stack.
bzr revid: vmt@openerp.com-20110914104300-n0l3dnmdu3jau7w2
the auth proxy was instanciated multiple times (once per handler instcance).
The previous refactoring merged the proxy and the provider in one class which
once instanciated once. Now it is instanciated once per handler, which is
better.
bzr revid: vmt@openerp.com-20110909122856-29uhsjfe193fqdi8
- grouped together the concept of auth proxy and auth provider
- removed the sec_realms dictionary: it was redundant as the
auth proxy was set (in one of the implementation, not all) on
the handler by setupAuth. Now the auth proxy is always set on
the handler.
- reg_http_service accepts the argument of the HTTPDir
constructor.
bzr revid: vmt@openerp.com-20110908123818-suc53zebgv9kcy3c
> gunicorn openerp:wsgi.application -c gunicorn.conf.py
If you want to try, you should know an addons_path is
hard coded in openerp.wsgi.on_starting().
bzr revid: vmt@openerp.com-20110819130248-tf81ttu42t2uhkuo
Vo Minh Thu
Olivier Dony
Antony Lesuisse