Am 31.10.2014 um 20:35 schrieb Stan Silvert
On 10/31/2014 2:46 PM, Heiko Braun wrote:
> The problem has nothing todo with GWT.
It has everything to do with GWT. The client code to deal with his
problem is 10x simpler in real Java. I know because I've coded both
> The single purpose of Haralds proposal is to reduce the number of requests and the
actual amount of data when querying large groups of servers. The native interface suffer
from this as well, it's just not that obvious because it's per se more performant
then the HTTP interface (optimised wire format, persistent connections, etc).
That's not true. Management requests are small, fast, and cheap. Doing
it over HTTP makes no noticeable difference.
The good thing about Harald's proposal is that it would make the code a
little simpler for Java clients and a lot simpler for GWT clients.
It's really about making management operations for big domains easier and more
performant. The current proposal is not meant to be a used as a query language. It's
purpose is clearly focused to read resources / attributes over deeply nested or
Whether the client is using GWT or any other language or framework is not the main focus
of the proposal. It just happens to fit quite well to GWT's asynchronous nature.
> On 31 Oct 2014, at 17:05, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
>>> Am 31.10.2014 um 17:03 schrieb Stan Silvert <ssilvert(a)redhat.com>:
>>> How much of a problem would this be if it were not for GWT's
callback-hell? It's my understanding that GWT is fixing that?
>> HAL is not the only client out there that needs that.
>> RHQ/JBoss ON can heavily benefit from that.
>> wildfly-dev mailing list
wildfly-dev mailing list
JBoss by Red Hat