Caching is a good idea, but Trac's dynamic nature makes it a little difficult.
The [[ChangeLog]] macro on TH illustrates the problem well. If this macro appears in a Wiki page the rendered version of the page can differ between one view and another, meaning it can not be reliably cached. If macros (plugins, etc.) could indicate to their rendering context whether they are cacheable, that would be a good start. Once that is possible, we can start sending back and handling cache control headers. On Fri, Feb 09, 2007 at 07:11:05AM -0500, Noah Kantrowitz wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I couldn't sleep tonight, so I thought I would take a look at this. > The code so far is up as http://trac-hacks.org/wiki/ > CacheSystemPlugin. Right now it only handle the wiki, and I can't > actually tell if it is any faster on here. The sun is coming up so I > should probably try sleeping again, but at least this is a start. > > - --Noah > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > > iD8DBQFFzGTZA9fEp2eRsU8RAvqyAJsHhPzwVny55OLe1p2m6f/ziJjn0ACgtlVO > U67AGESLgaVs4UH72HYtzZk= > =42Vd > -----END PGP SIGNATURE----- > > > -- Evolution: Taking care of those too stupid to take care of themselves. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
