Yes, that would be implemented in a BasePage class. I spent most of the day trying to get this and other solutions to work with the pageBlaster though, and there are conflicts that I have not been able to overcome (yet). Some of them use a unique key that should be returned in the page, but if the page is cached then that key won't change. Also, viewstate is pretty much request/user/session specific whereas with caching we want it to serve as many requests as possible with the same data, so they are really not compatible. I'm now really leaning towards compression with caching being the best overall solution, but I'll give it some more thought and maybe try to come at it from a different angle. |