Discrepancy between REST and remote API

Lukas Krejci lkrejci at redhat.com
Thu Jan 10 14:46:14 UTC 2013


Our remote API is not just for CLI. It's a generic remote EJB interface and we 
have clients using it, so we can't just dump it.

We could deprecate the remote EJB API, but I'd find it quite sad. If we based 
REST on remote API right from start, we could have had 2 interfaces to RHQ for 
free - we could support both REST clients as well as "heavy" java clients 
(that have the advantage of typed access, etc).

I would call it a failure on our side if we dropped/deprecated remote EJB API 
just because we'd find it hard to maintain and keep in sync with REST. This 
thing should be easy.


On Thursday, January 10, 2013 09:10:40 John Mazzitelli wrote:
> Perhaps the remote CLI could be retrofitted to use REST under the covers??
> 
> ----- Original Message -----
> 
> > Hi all,
> > 
> > REST has been gaining functionality that is not available through our
> > remote
> > API. Lately, it is the ability to create alert definitions, but it
> > also can
> > create dynagroups, afair, which is something remote API can't do
> > either.
> > 
> > While I welcome these additions and enabling remote users to achieve
> > such
> > things, I am also very concerned about fragmenting the capabilities
> > of the two
> > remote endpoints of RHQ.
> > 
> > I really do think that all the endpoints should be equal in their
> > capabilities. Not necessarily the APIs or approaches to getting the
> > data, but
> > the users should be able to achieve the same things regardless of the
> > endpoint
> > they use.
> > 
> > For this I think that ideally REST should exclusively use the remote
> > EJBs to
> > achieve its thing but that's not the case today. Because we are using
> > local
> > EJBs in REST, we are free to diverge as much as we want from the
> > remote API,
> > which I think is ultimately wrong and will only cause us problems
> > when REST
> > becomes stable and users will start asking questions why is this or
> > that
> > possible in REST and not in remote API (or vice versa).
> > 
> > Just my 2c, but I haven't heard any solid opinion on this problem or
> > how to
> > resolve it which is why I'm bringing it up here.
> > 
> > Lukas
> > 
> > _______________________________________________
> > rhq-devel mailing list
> > rhq-devel at lists.fedorahosted.org
> > https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
> 
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel


More information about the rhq-devel mailing list