How to server GWT pages from CDN network ?

[Ghostcoder]

My web application is taking quite some time to load .The HTML page is
around 215 KB in size and it has various other image and script files
which makes the size to 500KB .It takes around 25 to 30 secs to load
at my place where the speed is between 128 to 256 kbps sometime less
that that too .

This load time mentioned above is when it gets loaded the first
time ,later it takes only 5 to 6 secs to load as the pages are served
from that cache .I like to improve the first load time so I like to
server the HTML and images from CDN network .How do we configure GWT
to be served from CDN network .I need some clue as to how to
configure GWT to be served from CDN.

If I split the application into various modules will it help in
improving the load time ,but then I need to communicate between
modules, is that possible.

Thankyou .

[Ghostcoder]

I have seen some post on runasync feature in GWT ,I like to test that
feature can someone suggest the correct stable revision which i can
use to test this feature.

Do we need JAVA SDK 1.6 to build the source code in the trunk?

Thankyou

[lowecg2004]

I asked the same question a while back:

http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/3c06837fb6bfe732/5acff8e39b098cc2

I'll offer the same advice that I was given - search these forums for
info on "Same Origin Policy" (SOP). This is a restriction that
basically means you can only make RPC calls to the server that served
the page containing the GWT control rather than the server that served
the actual GWT html file assets. There's plenty of good information
in these groups on that subject.

What I had more difficulty in finding out however was that you'll also
need to add the following entry to your GWT project's XML config
(below your <inherits> entries):

<!-- Enable cross site location of GWT compiled assets. Required for
LIVE deployment only. Will not work in hosted mode. -->
<add-linker name="xs" />

As the comment suggests, this config will *not* work in hosted mode,
so you'll need to have different config files for development and
production environments.

From personal experience, I moved the deployment all my static assets,
inc. GWT html files, to Amazon's CloudFront and saw an absolutely
amazing improvement in the perceived performance of my application.

Good luck,

Chris.

[Ghostcoder]

Thanks for that information Chris ,I will give Runasync option a shot
to improve my load time, if not good then I will have to go with the
CDN approach.

Thanks

On Mar 30, 1:41 pm, lowecg2004 <chris.lowe...@gmail.com> wrote:
> I asked the same question a while back:
>

> http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa...

>
> I'll offer the same advice that I was given - search these forums for
> info on "Same Origin Policy" (SOP).  This is a restriction that
> basically means you can only make RPC calls to the server that served
> the page containing the GWT control rather than the server that served
> the actual GWT html file assets.  There's plenty of good information
> in these groups on that subject.
>
> What I had more difficulty in finding out however was that you'll also
> need to add the following entry to your GWT project's XML config
> (below your <inherits> entries):
>
> <!-- Enable cross site location of GWT compiled assets. Required for
>      LIVE deployment only.  Will not work in hosted mode. -->
> <add-linker name="xs" />
>
> As the comment suggests, this config will *not* work in hosted mode,
> so you'll need to have different config files for development and
> production environments.
>
> From personal experience, I moved the deployment all my static assets,
> inc. GWT html files, to Amazon's CloudFront and saw an absolutely
> amazing improvement in the perceived performance of my application.
>
> Good luck,
>
> Chris.
>
> On Mar 30, 7:59 am, Ghostcoder <thanneer.ma...@gmail.com> wrote:
>

> > I have seen some post onrunasyncfeature in GWT ,I like to test that