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 [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
-~----------~----~----~----~------~----~------~--~---

Reply via email to