Re: [Phpwiki-talk] Ampersand

[Jeff D. <da...@da...>]

On Sun, 23 Feb 2003 01:06:41 +0100
Martin Geisler <gim...@gi...> wrote:

> Jeff Dairiki <da...@da...> writes:
> > One of these days, (after user-auth and other things have
> > stabilized) it might be good to refactor the backends and SQL schema
> > a bit.
> 
> I think that would be nice. I noticed how the database is locked and
> unlocked with each operation, even on backends like PostgreSQL (and
> now also MySQL with InnoDB) that support transactions. This seams to
> be something that could benefit from a cleanup.

(Of course one of the big headaches is to optimize the schema while
keeping
the backend API general enough that we can write and maintain the
non-SQL backends (dba, flat-file) as well.  Also, it's good to share code
as much as possible between the different flavors of SQL, otherwise
we get all kinds of funny bugs creeping into the lesser-used backends...)


> A similar thing would be a plugin that generates an index like the
> ones you find in the back of most books. I'm not sure if this can be
> done automatically, but the plugin could skip words that appear on
> more than perhaps 10% of the pages or something like that. And it
> should also skip words on a stoplist.

That's an interesting idea.  I'm beginning to think about a more a general
API to allow caching of plugin ouput (this would be integrated with the
caching
of marked-up page content).   Once that's in place a plugin like
that would be viable.  (Until then ... its worth playing with but is
going to be slow.)

A related idea would be a way to manually enter search terms on pages.
E.g. something like "<?plugin Keywords platypus, funny animals ?>"
These could be used to form a real book-style index, and to generate
a meta keywords tag for search engines...  Basically the same as
Category pages, I guess...

(Maybe we should generate a keywords meta tag from Category links on each
page?)

Okay, so now I'm just rambling....