openerp-expert-framework team mailing list archive

[Raphael Valyi <rvalyi@xxxxxxxxx>]

Hello,

I also vote for this, thank you Nicolas to point it out, hopefully there is
time and resource for that for 6.1.

But also, I must say I see 0 valid reason that the "server" layer itself
doesn't enforce similar standard. Today the HTTP (XML/RPC) server layer is
easily a vulnerable point of the OpenERP architecture if exposed, so I think
you should be able to run the server layer on Apache or Ngnix or Twisted in
a similar way, even if the NetRPC hacky protocol could be still be something
artisanal in the meanwhile. Notice that there are such professional grade
servers where objects are passed serialized such as NetRPC. In the Java
world specifically, J2EE servers expose business objects in standard way via
the Enterprise JavaBeans.

Don't get me wrong I'm not telling we should be that bloated, and I'm not
for that serialized non cross platform format AT ALL. I very much prefer the
open world of the Internet with XML and HTTP messages if not REST. Meaning
ideally, NetRPC or even better a JSON layer at the "server" level such as
Tryton has already (and not an extra layer forcing to double
marshall/unmarshall the stuff as the new web-client) should be first
citizens of the platform and should be exposed on standard robust
webservers. I only wanted to tell that even frameworks that went for
serialized non cross language formats could still adopt standards and
OpenERP not (is there such a popular server standard for serialized objects
in the Python world?).

Only exposing the NetRPC and closing the XML/RPC to the world is also
equivalent to shooting yourself in the foot: OpenERP today is a relatively
nice SOA oriented framework that you can connect to anything, where you can
do by webservices everything you do in the user interface. This for instance
a  much better situation than they Magento where the WS layer is only a
crappy addon layer and where most of the time you can just not do by WS what
you would do in the UI. Even Openbravo copied that concept now, exposing all
there CRUD services RESTfully (over Jersey I Believe; notice that unlike
OpenERP, I believe they still miss 50% of the business logic at the WS
layer, but not 100% sure). So having an open interoperable WS layer is a
very strong point of OpenERP IMHO, so please don't kill that but let's make
it more professional; not only the HTML layer!

So yes, please do increase the user base of OpenERP. For that there is only
one way: decrease the entry barrier for the integrators (existing or new
ones) by making it more compliant with the well known and documented and
robust standards. I think this is a high priority.

Best regards.

-- 
Raphaël Valyi
Founder and consultant
+55 21 3010 9965
www.akretion.com



On Fri, Apr 29, 2011 at 4:39 AM, Nicolas Bessi <nicolas.bessi@xxxxxxxxxxxxxx
> wrote:

> Hello everybody.
>
> 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, but also we should be able to launch
> the server as a mod python for Apache or nginx.
> Such kind of integration will be really important in order to have all
> static content serve by powerful engine, enable load balancing etc…
>
> What do think about that.
>
> Regards
>
> Nicolas
>
>
>
>
>
>
>
> --------------------------------------------------------------------
> *Nicolas Bessi *
> Senior ERP consultant
> Business Solution technical director
>
> Camptocamp SA
> PSE A
> CH-1015 Lausanne
> http://www.openerp.camptocamp.com
>
> Phone: +41 21 619 10 26
> Office: +41 21 619 10 10
> Fax : +41 21 619 10 00
> --------------------------------------------------------------------
>
>
>
>
>
>
>
>
>
> _______________________________________________
> 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
>
>