nice talk, and how the used some of the upcoming features in GWT 2.0 to solve some of their issues... looking forward to GWT 2.0
but one thing struck me as funny... early in the talk, the espouse the fact that the used alot of code generation using Google Protocol Buffers http://code.google.com/apis/protocolbuffers/ as a data exchange mechanism between the UI and server... then bemoan the fact that the size of their downloaded javascript ballooned to "millions of bytes", like... no kidding!!!! they then use runAsync() to fix the problem by downloading code on an as needed basis. runAsync() is really nice, but they created their own problem by technically making hundreds of DTO's that are Domain Objects compiled into the javascript. Like I need to repeat this again.... runAsync() is just a patch to their issue as I see it, eventually you WILL have to download all of those "millions of bytes", where a more abstract data model would have avoided this. It looks like they tried JSON, but like me, found it "heavy handed" Interesting lessons, interesting solutions. Personally, I LIKE the fact that I can DL the whole app at once, and cache it, as long as I can keep it under control. On a project at Citi 2 years ago, I had an app with 50-60 screens, validation, etc.. in 800k on the wire. On Jun 4, 11:38 pm, Freddo <[email protected]> wrote: > Worth taking a look to see how Google does > ithttp://code.google.com/events/io/sessions/GoogleWavePoweredByGWT.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
