It won't generate different flavours. Otherwise, adding an RPC class would add at least 1 permutation (which it doesn't).
http://code.google.com/p/google-web-toolkit-doc-1-5/wiki/DevGuideDeferredBindingConcepts It needs to dynamically create an asynchronous proxy class for the synchronous definition, which can only be done using deferred binding. On Thu, Apr 23, 2009 at 8:58 AM, JoeB <joe.berm...@gmail.com> wrote: > > I understand the general concept of deferred binding, and how it > generates different flavors of JavaScript code at compile-time that > are selected at run-time based on the client's browser and locale. > What's unclear to me is why and how the GWT-RPC mechanism uses it. I > don't see why RPC needs the same kind of flexibility as browser > support and i18n. Can someone explain the concept behind this? > Thanks. > > -- Joe > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
