On Fri, Aug 7, 2009 at 2:50 PM, George Georgovassilis < [email protected]> wrote:
> > This occurred to me also when I started cutting down the requests: you > cannot do the initial selection on the server as HTTP proxies will > then see only one permutation: the first one that is ever retrieved by > them. > > I've reduced the total number of HTTP requests required to load to > just 2 (1 for the initial module html and 1 for the .cache.html), but > as stated earlier, inlining does not work as smoothly as Bruce (and > for that matter, me also) wants it to. First you have to (manually/ant > task) change the strings in nocache.js to prepend the actual path to > XYZ.cache.html, and then RPC will get back to you because > the .cache.html scripts disagree with the serialization policy about > the service entry points. > > So, is there a clean way? > With server-side selection, it just works. All you have to do is create the host page template so it can fill in the compile output name, write server equivalents for any custom property providers you have, configure your servlet container properly so the server components can intercept the request for the host page (if you aren't using Java on the server you will have to recreate that functionality) and inherit the right .gwt.xml file to pull in the server-side selection linker. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
