> I removed all caching from the WikiTalk engine, which is why CacheNone went > away. Caching now lives in the core, specifically in the content pipeline > between security and parsing. Right now we cache only the parsed > representation of a page, which is the most expensive thing to calculate. > The wikitext itself is actually retrieved every time. That's the most likely > next optimization, assuming we actually need any more. >
So, is using ExportMethodFlags.Default correct? > Sorry, no. I posted messages to this list over the years (years!) about the > changes I was making, and why, so you can search the archives for "FlexWiki > 2.0 Progress Report" to get a flavor of it, but the job of doing the changes > *and* documenting them all was simply too much for me. Sorry. > > I'm more than happy to answer questions here if anything is unclear. > I'll just start one up on my flexwiki.com page[1]. We'll see how useful it is to anyone else, (me included since I've already done my two plugins...) I suppose that it might be useful if/when we do the Parser stuff... I never heard back from or got with Vladimir on the parser, but I *think* that I'm getting to a place at work/home where I'll finally be able to take a look at it. [1] http://www.flexwiki.com/default.aspx/FlexWiki/NathanJones.html ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
