[cvs] [Wiki] changed: Project/ContentBackend

Chuck Hagenbuch chuck at horde.org
Mon Jun 30 05:06:02 UTC 2008


chuck  Mon, 30 Jun 2008 01:06:02 -0400

Modified page: http://wiki.horde.org/Project/ContentBackend
New Revision:  1.2
Change log:  note on search + perms

@@ -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/)
+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.

  +++ 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