On Friday, December 28, 2012 12:33:19 AM UTC+1, Goktug Gokdogan wrote:
On Fri, Dec 21, 2012 at 8:20 PM, Thomas Broyer <t.br...@gmail.com> wrote:
On Saturday, December 22, 2012 2:50:00 AM UTC+1, Goktug Gokdogan wrote:GWT's built-in library space is already bloated and getting harder to maintain. Inside GWT, we need to do less but do better.And good thing is, a lot of stuff doesn't need to be baked in; like the protocol buffers; it is a valuable feature but I personally don't see GWT having it as a first class citizen; at least in the near term.On the other hand we can definitely help out on removing any blockers and support anybody who would like to implement it as a 3rd party library.+1
Wondering what Google is doing though ;-)Are you somehow generating, say, RequestFactory ValueProxy-s from .proto files? It looks like what BobV was planning.There is compiler plugin that generates lightweight GWT emulations of the messages based on JavaScript overlays.On top of that, there is a custom RPC mechanism that mimics GWT RPC. Wire format is like JSON-RPC where 'params' is js array encoded protobuf.I think there has been multiple solutions but I guess this one got wider acceptance. Unfortunately, nobody actively working on it and not ready to open-source.
Thanks.
Looks a bit like what I did years ago to call "REST-alike web services", except I coded everything by hand.
Also looks a bit like gwt-json-rpc used by Gerrit, but interfaces and JSOs are hand-coded too.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/1rV1RZB55M4J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment