openerp-expert-framework team mailing list archive

[Zyphos <zyphos@xxxxxxxxx>]

You are perfectly right, Pyro was out of my head.
This should be included in core too.

borjals a écrit :
> Zyphos [via openerp-expert-framework] escribió:
>
> > - "Xmlrpc2", for now, openerp is not really based on session. So the
> > creditential needs to be sent
> > each time.
> > If you want to spare bandwith, you should use something like JSON, or a
> > binary format instead of the verbose XML as protocol.
> > For file (binary content), image, you should avoid those base64 encoded
> > content that take up to 33% more space. (37% in MIME mail)
> > http://en.wikipedia.org/wiki/Base64
> >
> > You can use something like: BasE91 about sparing 7 to 14%
> > http://base91.sourceforge.net/
> >
> > Or But by removing base64 => you MUST use a binary protocol. (Because
> > specials char can be use in binary) => sparing 33%
> > Binary needs to pickle, and is exposed to buffer problems (overflow and
> > so one), needs to take care of type of CPU (low-end encoding, high-end
> > encoding), float representation, and so on.
>
> Aren't we reinventing the wheel here?
>
> I mean, if you take a look into the Koo (OpenObject KDE client) client
> repository ( https://code.launchpad.net/openobject-client-kde) you will
> notice that it already may use a statefull protocol to connect to
> OpenERP server: Pyro!
>
> The Koo project already includes a server module (for OpenERP 5.0
> version;
> http://bazaar.launchpad.net/~openobject-client-kde/openobject-client-kde/5.0/files/head%3A/server-modules/pyro/
> <http://bazaar.launchpad.net/%7Eopenobject-client-kde/openobject-client-kde/5.0/files/head%3A/server-modules/pyro/> 
>
> <http://bazaar.launchpad.net/%7Eopenobject-client-kde/openobject-client-kde/5.0/files/head%3A/server-modules/pyro/>)
>
> that provides that Pyro protocol support. So on the server side the only
> thing left to do is include it on the base server.
>
> Pyro is statefull and fast and does all the hard work for us, as it is a
> object-oriented RPC-like protocol (http://pyro.sourceforge.net/). And
> has been already tested by the KDE client.
>
> Thanks to Pyro, and some other optimizations, the Koo client overall is
> one order of magnitude faster than the GTK client over slow or
> high-latency networks (DSL/Cable).
>
> -- 
> Borja López Soilán
> [hidden email]
> <http://n3.nabble.com/user/SendEmail.jtp?type=node&node=453130&i=0>
>
> Pexego Sistemas Informáticos S.L.
> Avenida de Magoi 66 - 27002 Lugo (España)
> Tel./Fax 982801517
> http://www.pexego.es 
>
>
> ------------------------------------------------------------------------
> View this message in context: Re: Doc of experimental features
> <http://n3.nabble.com/Doc-of-experimental-features-tp451889p453130.html>
> Sent from the openerp-expert-framework mailing list archive
> <http://n3.nabble.com/openerp-expert-framework-f71550.html> at Nabble.com.
> ------------------------------------------------------------------------
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-framework
> Post to     : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-framework
> More help   : https://help.launchpad.net/ListHelp
>