> OK. I was under the impression that the cache was implemented on the Rails > side, in the same fashion that people write page caches in Java on the Servlet > side.
That would be what's called action caching in rails. > Actually, I'm starting to wonder why Apache doesn't do this caching instead of > needing to implement it manually on the Rails side. Really, a webapp should > only have to put the right cache headers on the pages it returns And how do you invalidate cached pages ? > reason, though... so that they can get caching on anything without writing any > code. You still have to decide to cache such asd such pages and to uncache on some events, and typo does just that. > I suppose if the admin markup were served using AJAX calls which were > initiated > only for admins, that would solve both issues. It's just nudging the 'problem', that ajax code has to be server to everyone. -- D
