8:28 p.m.
On Jan 22, 2015, at 3:48 PM, John Sanda <jsanda(a)redhat.com>
wrote:
On Jan 21, 2015, at 3:04 PM, Heiko Braun <hbraun(a)redhat.com
<mailto:hbraun@redhat.com>> wrote:
>
> Some additional information regarding the wildfly integration and the rest interface
in particular:
>
> Any subsystem in wildfly can register an undertow HTTP handler or an undertow HTTP
upgrade handler. The HTTP handler exposes the regular undertow API for building HTTP based
endpoints [1]. This one should be straight forward to use for implementing the REST
interface you currently have in rhq-metrics.
>
> The upgrade handler on the other hand does HTTP upgrade to a custom protocol of your
choice (if needed in the future). It can as well be used to provide web socket based
access to your services.
>
> Taking into consideration that undertow can also be easily embedded [2] I think this
covers a lot of ground.
>
> Regards, Heiko
>
> [1] http://undertow.io/documentation/core/undertow-handler-guide.html
<http://undertow.io/documentation/core/undertow-handler-guide.html>
> [2] http://undertow.io/documentation/core/bootstrapping.html
<http://undertow.io/documentation/core/bootstrapping.html>
>
Thanks for the info Heiko. Here is what we need to figure out. Provided that all of the
business logic resides in the core service, would the amount of work involved with
building another implementation with undertow be small enough that it would be worth have
the two implementations. If the amount of work is small, would this be something you (and
by you I basically mean the WF team) would be comfortable owning?
One thing that comes to mind is the keycloak integration. I am not how much
effort/duplication would be involved. If it does look like it will be a lot of effort
and/or duplication, then we really need to consider a more minimal stack without JAX-RS.
I have another, somewhat related question. The LiveOak project is also working with
hawkular-metrics. I think that they are deploying the metrics war side by side with their
stuff. If we wind up with a more minimal implementation as you describe, how would that
work with LiveOak which is ok with consuming a war since they are running in a server that
already has war deployments, JAX-RS, etc.?
- John
The more I think about this the more I think that the hawkular team should own this. One
of the initial requirements for metrics early on was minimal dependencies in order to make
it easy to embed. Stefan said he would start looking into an implementation built on
undertow core. As far as the questions around maintaining the current JAX-RS
implementation versus (or in addition to) something else, I do not think we need to rush a
decision. I think we ought to at least get a working prototype in place and then revisit
that discussion.