Thanx Ikai, that was the final answer we were waiting for. We now have a good solution for serving more than 3000 GWT generated files efficiently :-)
François On Tue, Sep 14, 2010 at 22:12, Ikai Lan (Google) <[email protected]<ikai.l%[email protected]> > wrote: > I wouldn't call it a CDN, but the caching infrastructure at Google may hold > on to static assets with the correct headers set. One of the key benefits > here is that you won't be charged CPU time for serving the asset, though > bandwidth charges will still be applied. This is only a best effort caching > and is not guaranteed, so in the worst case scenario the caching > infrastructure will not hold on to your data and the requests will still be > routed to your application instances. > > On Tue, Sep 14, 2010 at 12:57 PM, Francois MASUREL <[email protected]>wrote: > >> Full answer there : >> >> http://www.kyle-jensen.com/proxy-caching-on-google-appengine >> >> >> >> >> On Tue, Sep 14, 2010 at 21:47, Stephen <[email protected]> wrote: >> >>> >>> >>> On Sep 13, 5:25 pm, Francois Masurel <[email protected]> wrote: >>> > Let me explain : >>> > >>> > I have potentially too many (> 3000) GWT generated files in my java >>> > application. I've already packed all my java classes in a jar. >>> > >>> > So I made a zip of all these files and implemented a servlet to serve >>> > them dynamically. >>> > >>> > The servlet url-pattern matches an include path defined in my >>> > appengine-web.xml static-files block. >>> > >>> > The question is : will the files served by my servlet be cached on >>> > Google CDNs as supposed in this thread : >>> > >>> > http://groups.google.com/group/google-appengine/browse_thread/thread/. >>> .. >>> > >>> > It doesn't seem to be the case as each time I purge my browser cache, >>> > the files are served again from my servlet. >>> >>> >>> http://code.google.com/p/googleappengine/issues/detail?id=2258 >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google App Engine" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<google-appengine%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine?hl=en. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-appengine%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en.
