Gary, You're quite right that the API I'm referring to is nonexistent. My point was that what your suggesting seems to be a replacement for GWT- RPC and the compiler. I think the compiler and RPC are great as engines. I would just like to not have to build my own steering wheel every time I use the car, metaphorically speaking.
On Aug 12, 12:02 am, Gary Miller <miller.ga...@gmail.com> wrote: > @Miroslavhttp://code.google.com/events/io/sessions/GoogleWavePoweredByGWT.html > Worth watching or looking through the slides. > > On Aug 12, 3:37 pm, Miroslav Pokorny <miroslav.poko...@gmail.com> > wrote: > > > > > @Gary > > I have not seen the GoogleIo vid, why do you say wave uses json AND > > protocol buffers to talk between client <-> server...? > > > On 12/08/2009, at 11:01 AM, Gary Miller <miller.ga...@gmail.com> wrote: > > > > I agree the problem is begging out for a more elegant solution. > > > From the Google IO presentation on Google Wave powered by GWT a > > > solution using proto buffer and JSON instead of GWT RPC is mentioned. > > > I've been thinking that a similar result could be achieved annotation > > > the server side object model with annotation (e.g. jsonmarshaller > > >http://code.google.com/p/jsonmarshaller/) and the generating the > > > client side JavaScriptObject code using an annotation processor. > > > > Thoughts? > > > > Gary --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
