Hi Sergio, > I'm thinking in a Filter that put page results in memcache when first > accessed, and then getting that result in former accesses.
That should work. All page cache implementations do more or less the same. > The idea is simple but the implementation is not. (how to get the > first request response? how to implement proper header management in > that filter? how to not disable gzip using this?) * If there is content in memcache, you can deliver it and exit. Otherwise, let the request proceed, and store in the cache. * Be sure to set the cache timeout and calculate the cache key correctly (e.g. include the user ID or the user locale if the cached contents depend on that). * For HTTP headers, this presentation may help: http://www.slideshare.net/icoloma/caching-web-contents-in-the-browser-999134 It's more or less the same with JSP page fragments (except the headers, of course). No rocket science. Cheers, Nacho. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
