On 22 oct, 09:52, abhijeet <[email protected]> wrote: > We have product, who's front end is in GWT. As it contains many > classes (Around 150 menus, you can imagine now) > > When user access this first time, it takes time to load. (If > bandwidth is low then this increases) > > next time on wards it remains in catch, we dont have to worry about > bandwidth. > > Can i reduce this first time app loading time by using GWT deferred > binding ?
Just to clarify (because Didier gave the correct answer): "deferred binding" means deferring at runtime the "choice of the actual implementation" of a given class or interface. The choice is based on the values of "deferred binding properties"; those values (actually, the choice between the available values that a property can take, as defined at compile-time) are evaluated at runtime (or can be fixed to a single possible value at compile time) through "property providers" (snippets of JavaScript code). This is done by generating a script for each permutation of property values (the *.cache.html files) and choosing which one to actually use from the "selection script" (the *.nocache.js file). The selection script just calls each "property provider" to accumulate the complete set of "runtime values" for the properties, so it can choose the actual "permutation" to load. As you can see, there's nothing about "lazy loading". (note that technically you could evaluate some of the properties on the server side, and in some cases –as is done within Google Wave– even bypass the "selection script" and choose the permutation on the server-side, but still at runtime; this is however requires very advanced knowledge of GWT internals) -- 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.
