concept difference in category gwt

This is an excerpt from Manning's book GWT in Action.
This is a simple application with only one module; a more complicated application could have more modules. In section 2.5.2 we’ll discuss this in a little more detail together with module naming and how to tell the difference and the relationship between GWT modules and Java packages.
You use deferred binding when you need to handle differences in code. The most common difference you’ll need to handle is the various implementations of DOM in the assorted browsers. (GWT hides most of these differences from the programmer by making heavy use of deferred binding, as you’ll soon see.)
GWT provides a way of solving both of those problems: deferred binding. It harnesses the power of Java to manage differences in your source code (reduces the maintenance and debugging problem), and the GWT compiler automatically creates several JavaScript versions of your application, called permutations. These permutations each contain only the code for one combination of differences (smaller code download equals an enhanced user experience). The compiler also produces some bootstrapping code that determines which permutation the user requires based on resolution of one or more properties. Differences are identified by the use of a property that can have one of several predeclared values. In the GWT bootstrap code the compiler inserts a property provider—a segment of JavaScript that determines the precise value of the property for this implementation—and downloads the appropriate permutation.
The ranges of differences that can be in a GWT application is defined by a set of property values and the values they can take. You’re free to define your own properties, which we’ll look at in section 17.3, but you have some built-in ones as well, such as for browser rendering engines and locales.