odoo
/
odoo
2
0
Fork 0
Code Pull Requests Releases Activity

[DOC] openerp.http: use sphinx domains. 

bzr revid: vmt@openerp.com-20130201151354-uyxgyt0aw101a2mq
This commit is contained in:
Vo Minh Thu 2013-02-01 16:13:54 +01:00
parent c8ffd1cedc
commit 56df6d6ecc
2 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/routing.rst
View File

@ -12,9 +12,16 @@ endpoints.
In older version of OpenERP, adding RPC endpoints was done by subclassing the
``openerp.netsvc.ExportService`` class. Adding WSGI handlers was done by
registering them with the ``openerp.wsgi.register_wsgi_handler()`` function.
registering them with the :py:func:`openerp.wsgi.register_wsgi_handler`
function.
Starting with OpenERP 7.1, exposing a new arbitrary WSGI handler is done with
the ``openerp.http.handler`` decorator while adding an RPC endpoint is done
with the ``openerp.http.rpc`` decorator.
the :py:func:`openerp.http.handler` decorator while adding an RPC endpoint is
done with the :py:func:`openerp.http.rpc` decorator.
Routing decorators
------------------
.. automodule:: openerp.http
:members:
:undoc-members:

4
openerp/http.py
View File

@ -1,8 +1,8 @@
# -*- coding: utf-8 -*-
"""
Decorators to register WSGI and RPC endpoints handlers. See doc/routing.rst.
# TODO use sphinx ref to doc/routing.rst.
``openerp.http`` offers decorators to register WSGI and RPC endpoints handlers.
See :ref:`routing`.
"""
from . import service