Endi, My apologies. I mean that you can allow S3/Cloudfront to serve all static resources (html/js/img/tile/sound) so that your servers don't have to carry this load. Given that GWT makes all of the UI into static resources, this means your entire UI needs no dedicated machines. Since CloudFront allows forwarding, yourDomain.com/api/ can pass through to your backend servers, and if you return cache headers (i.e. 10min) you can let the CDN buffer your API as well. Given S3/CloudFront are nearly infinitely scalable, it might make life easier when things go viral for you (which we hope they do!).
Anyway, I was just noting how wonderful GWT is with CDN's, since you can make a app server that is just an API server, which is much cleaner than the typical Java, everything in one massive .war option. BTW, 48GB is huge! Sounds like a fun challenge. It would be great to learn more details of your app as it is developed further. Please do keep us informed. 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. For more options, visit https://groups.google.com/d/optout.
