Curious if anyone has had experience hosting GWT app resources on S3?

There are two ways you can approach it:

   - Host all of the compiled GWT output on S3 and relay dynamic requests 
   through S3 to your server (i.e. XHR/POST)
   - Host your static resources on S3, but load the initial .html page and 
   no-cache from your server

I was planning on the second mechanism as it would be easier to dev/test 
and would not require S3 dependence (i.e. you can put the static content 
wherever).

However, I was curious how people have configured resource bundles in GWT 
to point to a separate server than the one the application was loaded from. 
So, *does anyone have experience configuring the GWT linker to point to a 
separate host for static content?*
*
*

Or, restated

   - all async's must point to the origin server
   - all resource loading requests must point to a different static file 
   server


Thanks for your thoughts.



Sincerely,
Joseph

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to