We launched our GWT production of http://www.holidayinn.com few months
ago and we are in the phrase to tune the performance.
We see quick high percentage of traffics coming from nocach.js and
cache.html, and just thinking how to reduce over all traffics.
The normal flow of GWT would be like followings:
1) The user request the website, the first server call is to get
generated html file (from JSP/Servlet)
2) Then browser sends second request to fetch nocach.js with
<script type="text/javascript" language="javascript" src="/
directory/xyz.nocache.js"></script>
3) Based on the user browser's type, the browser send third request to
get .cache.html
4) Few RPC calls to get real content.
So at least three requests are executed in sequence before the user
can see something. It is kind of expensive.
Technically, in the very first request, the server already knows user
browsers' type, is that feasible to:
combine 1), 2) and 3) together or
combine 1) and 2) together or
some other consideration
Would like to hear your opinions.
Thanks
--Michael
--
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.
