[pmwiki-users] deprecating PCache (Was: Re: PageLists of database contents)

[Dominique Faure]

On 10/5/06, Patrick R. Michaud <pmichaud at pobox.com> wrote:
> On Wed, Oct 04, 2006 at 03:00:59PM -0700, Martin Fick wrote:
> > --- "Patrick R. Michaud" <pmichaud at pobox.com> wrote:
> Only those recipes that are directly accessing
> $PCache, which I've tried to discourage over time.
> Everything else ought to be plug compatible (or made to
> be that way).
>
> > > I wasn't planning to revamp
> > > $PCache for 2.2... but with the pagelist and page
> > > variable changes it's becoming far more relevant,
> >
> > Break it now, pmwiki will be awesome!  Even though it
> > might break recipes, many of them could be eliminated
> > or greatly enhanced/simplified with these features
> > anyway,
>
> I don't think I'll do this for 2.2.  PageStores need to be
> substantially redesigned anyway to handle non-ASCII
> characters in filenames, and case-insensitive pagnames
> on case-sensitive filesystems, and spaces in pagenames,
> and a bunch of other things that need addressing.
> So, if changing PCache and search are going to require
> substantial modifications to PageStore, it'll probably
> have to wait for 2.3, because unless I suddenly have a
> bunch of breakthrough ideas on some of these other
> PageStore-related items it would hold up the 2.2
> releases for far too long.
>
> Besides, a deprecation cycle for $PCache would give
> recipes an opportunity to migrate away from using
> it before making a switch.
>

Then, I would suggest that you could easily provide a kind of API to
allow (core and) recipes to maintain page related information during
the parsing instead of directly using $PCache for that -- in the same
way you already designed the ParseArgs() function.

Dom