openerp-expert-framework team mailing list archive

[Raphael Valyi <rvalyi@xxxxxxxxx>]

Hello Antony,

this sounds pretty good!

Questions:

1) what about the XML/RPC secure? will that be still supported? What URL
then? Or will you advise to use standard XML/RPC but behind some HTTPS
reverse proxy?

2) Also, what is the progress with the JSonRPC, is there some code
somewhere, does it or will it support all he features we have with XML/RPC
currently? So you think it will make it into 6.1 ? If jSonRPS is supported,
will the Javascript of the new web-client use it or will it use yet a new
JSon ad-hoc layer?

3) Also, the web-client has session support which is a lot better for the
security (not all requests carry your password). Is it still specific to the
web-client? Any chance this session support is extended to the usage of the
other cross platform protocols (XML/RPC and may be true JSonRPC)?

4) Finally, I think JSonRPC is a very good evolution. But I still fell we
miss the REST goodness of respecting the existing HTTP semantic. Like
idempotence and cache-ability of GET requests, possibility of e-tags etc...
could be very useful to scale OpenERP to hundreds of users who might not all
need always realtime data (ACID for everybody is cool but it just doesn't
scale). What is OpenERP SA vision about that?


Thanks and kudos for the move.

-- 
Raphaël Valyi
Founder and consultant
+55 21 2516 2954
www.akretion.com



On Thu, Sep 1, 2011 at 9:15 AM, Antony Lesuisse <al@xxxxxxxxxxx> wrote:

> We are currently wsgifying the openerp-server:
>
> https://code.launchpad.net/~**openerp-dev/openobject-server/**
> trunk-xmlrpc-vmt/+merge/71827<https://code.launchpad.net/~openerp-dev/openobject-server/trunk-xmlrpc-vmt/+merge/71827>
>
> Openerp-server only listen to 8069 and any module is able to map a an url
> to it's own wsgi handler. /openerp is a reserved namespace and the following
> routes is setup by default.
>
> /openerp/jsonrpc -> jsonrpc api dispacher
> /openerp/xmlrpc -> xmlrpc api dispacher
>
> For example the webdav module will register to route:
>
> /webdav -> webdav wsgi handler
>
> The trunk webclient is currently using cherrypy as http server, http
> request object and http session object, we plan to switch to werkzeug
> (branch to merge). The file openerp-web.py simply setup a cherrpy http
> server and dispatch request to the 'base' web module (i plan to rename base*
> into web*).
>
> http://bazaar.launchpad.net/~**openerp/openerp-web/trunk/**
> view/head:/openerp-web.py<http://bazaar.launchpad.net/~openerp/openerp-web/trunk/view/head:/openerp-web.py>
>
> Once the openerp-server is wsgi ready we could put the webmodules in
> addons-path and have the 'base' web module register a wildcard route
>
> / -> web handler
>
> In this mode the rpc communication between the web client and openerp
> server is replaced by direct function calls. See the files backendrpc.py vs.
> backendlocal.py here:
>
> http://bazaar.launchpad.net/~**openerp/openerp-web/trunk/**
> files/head:/addons/base/**common/<http://bazaar.launchpad.net/~openerp/openerp-web/trunk/files/head:/addons/base/common/>
>
> The advantages are:
>
> - speed rpc replace by function calls
> - no more downloading modules from openerp-server as zip file into web
> addons (something i really dislike), the 'web' module scans for other addons
> in addons-path.
> - in multiprocessing mode workers are managed by the same dispatcher as the
> regular openerp-server worker
> - there is only one openerp-server. it's an http server. no more confusing
> name like 'web client'.
>
> Of course the standalone mode is still available, so it's the best of both
> world.
>
> Any feedback ?
>
> Antony Lesuisse
>
> ______________________________**_________________
> Mailing list: https://launchpad.net/~**openerp-expert-framework<https://launchpad.net/~openerp-expert-framework>
> Post to     : openerp-expert-framework@**lists.launchpad.net<openerp-expert-framework@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~**openerp-expert-framework<https://launchpad.net/~openerp-expert-framework>
> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>