[cvs] [Wiki] changed: Project/ContentBackend
Chuck Hagenbuch
chuck at horde.org
Mon Jul 21 03:16:20 UTC 2008
chuck Sun, 20 Jul 2008 23:16:20 -0400
Modified page: http://wiki.horde.org/Project/ContentBackend
New Revision: 1.3
Change log: sphinx
@@ -27,9 +27,9 @@
If possible performance-wise, a Horde-wide content tagging
implementation, using content_master_ids, would allow relating tagged
content between multiple Horde applications or content types.
+++ Search
-Once we have Horde_Content, we should be able to build
Horde_Content_Index on top of it that builds a full text index of
anything in the horde_content_master table (using the content type
objects to fetch each piece of content for indexing), with either
mysql full-text as a backend, or something like Solr
(http://lucene.apache.org/solr/). One challenge is handling
permissions. Possibly we could store an object's permissions in the
search backend itself, and update them along with any other changes to
the object.
+Once we have Horde_Content, we should be able to build
Horde_Content_Index on top of it that builds a full text index of
anything in the horde_content_master table (using the content type
objects to fetch each piece of content for indexing), with either
mysql full-text as a backend (alternately
http://www.sphinxsearch.com/), or something like Solr
(http://lucene.apache.org/solr/). One challenge is handling
permissions. Possibly we could store an object's permissions in the
search backend itself, and update them along with any other changes to
the object.
+++ CMS front end?
I'm just going to preserve a quote from Duck here since I'm sure
there's something useful to be distilled from it but I'm not capable
of doing that distilling right now:
More information about the cvs
mailing list