I seem to remember this in another caching discussion: what about response headers? From what I recall, browsers won't allow you to use meta tags for evey header, so simply caching the html won't necessarily fill every need.
Could the caching scheme be extended to store and transmit cached headers as well? -Andrew On 9/13/07, Daniel Sheppard <[EMAIL PROTECTED]> wrote: > > So, this doesn't sound like a rewrite of Radiant yet, hence maybe I > > get something worthwhile by using Radiant as the starting point. > > > > Are there any changes to caching that we could consider for core > > which would also help make sense at this scale? > > I think that the caching is about as good as it's going to get, and without > hard numbers I'd suggest that handing the caching over > to apache probably isn't worth the effort. > > > Are there any changes to the Admin page interface ""? > > If your pages already have a natural heirachy that keeps the number of > children of a specific page fairly low (I'd say up to about > 20-30 should be fine), then I don't think you'll have a problem. > > If you've got something like my situation, where you're using something like > ArchivePage and letting it have a few hundred children, > then you'd want a way for a page type to be able to segment the child list > (ie, when expanding the archive page in the admin, > instead of directly expanding to the children, it provides a list of years > which expand into months). > > Dan. > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
