Jan Haderka ha scritto:
The problem is that out of the website workspace, the content is usually
not directly displayed so even if you get a hit, you have to somehow
device a connection between the piece of content that generated a hit
and the web page (content in the website workspace) as part of which
such a hit should be displayed ...
My question is: "why" is so necessary to query other workspaces?
I think that one solution can be to integrate in Magnolia (as a
separated module) something that thinks like Google: we are in a world
of pages: no matter where the "source content" is, we can try to index
the aggregation state of content.
Why not considering SOLR?
* http://lucene.apache.org/solr/
If a content from a data module is displayed in a website page, it
should be caught by solr indexing.
It is just a point of view...
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
