I'd like to address https://sourceforge.net/p/allura/tickets/6207/ soon. The summary is that we currently have a max char size for rendering markdown, since sometimes it can be extremely slow to render (and we've tried to improve that with no luck). A max char size is ugly though and we don't want that. We added caching for markdown rendering recently, but have only applied it to comments ("posts") so far. If we expand it to wiki pages, tickets, etc, then the max char limit can be removed or made much much higher. But it's more likely that a macro (e.g. include another page) will be used in wiki and tickets and then our simple caching strategy won't work well because the macro won't be re-run.
Anyone have ideas for how to do cache invalidation in that situation? One idea I have is pretty crude, but might work: check to see if there are any macros in the markdown (search '[[') and never cache those. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
