On 10/31/2014 2:40 PM, Heiko Braun
A lot of your particular problem is with GWT, and that is indeed a
topic for another thread.
Haralds proposal was designed to be orthogonal to the
concepts we currently have and embed within existing protocols
and API. The idea is to build something straightforward to solve
A query language sounds nice, but I don't really see how it
relates to problems described in the former proposal. If you
want to discuss that idea further, I would suggest to move it to
Herald's proposal is a good one and people would want to do more
with it than just solve your particular dilemma. Thus, it
eventually becomes more and more like a query language.
My point was just that if Herald is interested, he could easily do
this on the client side and move it to the server side after it
But if Brian wants to plow ahead on the server side that's good too.
Taken to its logical conclusion, this
would become a full-fledged query language.
You could just create a client-side
library for it and use that as the "language" develops. I
think that would be a safe thing to do before committing it
as part of the supported server side interface.
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?