[Cubicweb] Service API implementation with ømq

Sylvain Thénault sylvain.thenault at logilab.fr
Thu Mar 1 17:55:34 CET 2012


On 01 mars 17:34, Pierre-Yves David wrote:
> On Thu, Mar 01, 2012 at 05:28:02PM +0100, Sylvain Thénault wrote:
> > On 01 mars 10:51, Pierre-Yves David wrote:
> > > > On the repo side, simply type :
> > > > 
> > > >  vreg['services'].select(regid, session, **kwargs).call(**kwargs)
> > > > 
> > > > ie services may be used directly as other registry objects.
> > > 
> > > But this is different code than client side one. Having different API for the
> > > same thing is an hassle because this prevent your to write generic code running
> > > fine on both side. The API should be unified.
> > 
> > IMO generic code for server/web is currently badly achieved, and also need
> > for redesign. We won't try to unify this api until this is fixed, this is
> > to much pain for the gain. And even if I was happy with the implementation,
> > I don't see cases where we would need an unified service API.
> 
> I do not see how this is painful to unify this API. And I can provide patch if
> necessary.

Then provide a patch.
 
-- 
Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (09.54.03.55.76)
Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
CubicWeb, the semantic web framework:    http://www.cubicweb.org



More information about the Cubicweb mailing list