2009/10/23 Dmitriy Sintsov questpc@rambler.ru:
- My extension generates dynamical content. Because of that, I use
$parser->disableCache() in my tag parser hook. But, the dynamical content is being changed only in two cases:
a) The user edits the page. In such case, disableCache() is not required, because Article cache should be properly flushed by core.
b) The user submits the poll. After the processing of POST data I redirect with 302. In such case, which is the best way to conditionally flush the cache - will parser->disableCache() work after the POST and before the 302? To me it looks that it won't have an effect on the next GET after the redirect. Or, I'd better use Article::doPurge() (or, that is too slow?).
I think purging after the submission of the poll would probably be good enough, so you wouldn't need disableCache().
Roan Kattouw (Catrope)