On Fri, Aug 7, 2009 at 3:51 AM, George Georgovassilis
g.georgovassi...@gmail.com wrote:
I'd like to save first time visitors that roundtrip to fetch
nocache.js. Instead I've declared the module HTML page as non-
cacheable (works nice thanks to E-Tag) and moved images and GWT-
compiler
I'd be keen to see this land in trunk !
Cam
2009/8/7 John Tamplin j...@google.com
On Fri, Aug 7, 2009 at 3:51 AM, George Georgovassilis
g.georgovassi...@gmail.com wrote:
I'd like to save first time visitors that roundtrip to fetch
nocache.js. Instead I've declared the module HTML page as
I'd love to see this in the trunk too. We have only 2 round trips on
start up now, thanks to ClientBundle. Getting it down to one will be
very slick!
--
Arthur Kalmenson
On Fri, Aug 7, 2009 at 8:41 AM, Cameron Braidcame...@braid.com.au wrote:
I'd be keen to see this land in trunk !
Cam
2 requests is very impressive, Arthur! This is the sort of conscientiousness
(i.e. for optimizing user experience) I hope all GWT developers would strive
for. Nice work.
And yes, we'd like to help you get that down to 1, too.
On Fri, Aug 7, 2009 at 9:43 AM, Arthur Kalmenson
+1
On Aug 8, 8:43 am, Arthur Kalmenson arthur.k...@gmail.com wrote:
I'd love to see this in the trunk too. We have only 2 round trips on
start up now, thanks to ClientBundle. Getting it down to one will be
very slick!
--
Arthur Kalmenson
On Fri, Aug 7, 2009 at 8:41 AM, Cameron
Are you counting fetching the host HTML page? With this approach, the
selection script is done away with but you still have a fetch for the
compiled script so that it can remain permanently cacheable. You could
theoretically inline it into the host page, but since none of that is
cacheable
The best you can do for a cold cache is 2 round-trips (including the host
page) if you inline the selection script (.nocache.js) in the host page. You
definitely do want the compiled script (.cache.html) *not* embedded in the
host page, so that it can have cache forever semantics. Then, when users
On Fri, Aug 7, 2009 at 11:39 AM, Arthur Kalmenson arthur.k...@gmail.comwrote:
I don't think firebug counts the initial request to fetch the host
page, so two requests. One for the nocache.js and another for the
cachable HTML. With the inlining of the nocache.js file, you could get
it down to
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
Nevermind, solved my RPC-woes by copying the policy file to the web-
app root. Ugly, but down to 2 requests.
On Aug 7, 8:50 pm, George Georgovassilis g.georgovassi...@gmail.com
wrote:
This occurred to me also when I started cutting down the requests: you
cannot do the initial selection on the
On Fri, Aug 7, 2009 at 2:50 PM, George Georgovassilis
g.georgovassi...@gmail.com 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
11 matches
Mail list logo
