You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by ke...@apache.org on 2002/09/23 08:42:32 UTC
cvs commit: jakarta-lucene-sandbox/contributions/indyo/docs introduction.txt
kelvint 2002/09/22 23:42:32
Modified: contributions/indyo/docs introduction.txt
Log:
Fixed formatting.
Revision Changes Path
1.2 +24 -3 jakarta-lucene-sandbox/contributions/indyo/docs/introduction.txt
Index: introduction.txt
===================================================================
RCS file: /home/cvs/jakarta-lucene-sandbox/contributions/indyo/docs/introduction.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- introduction.txt 30 Aug 2002 17:57:30 -0000 1.1
+++ introduction.txt 23 Sep 2002 06:42:32 -0000 1.2
@@ -1,8 +1,29 @@
-Indyo is a datasource-independent Lucene indexing framework. What this means, is that Indyo allows a myriad of sources from which data is fed to the search engine to be indexed. Datasources can take the form of traditional storage mediums (filesystem, database, web site, etc), objects, complex datasources which consist of a mixture of objects and storage medium, and pretty much anything which implements com.relevanz.indyo.IndexDataSource. If it's a file that's being indexed (via com.relevanz.indyo.FSDataSource), the contents of the file can be indexed by a class which implements com.relevanz.indyo.contenthandler.FileContentHandler (e.g. TextHandler, ZIPHandler, etc). Via the datasource, applications can also associate a search result object with the object that was indexed (or optionally use Peter's SearchBean contribution), for display purposes.
+Indyo is a datasource-independent Lucene indexing framework.
+
+What this means, is that Indyo allows a myriad of sources from which
+data is fed to the search engine to be indexed. Datasources can take
+the form of traditional storage mediums (filesystem, database, web
+site, etc), objects, complex datasources which consist of a mixture of
+objects and storage medium, and pretty much anything which implements
+com.relevanz.indyo.IndexDataSource. If it's a file that's being
+indexed (via com.relevanz.indyo.FSDataSource), the contents of the
+file can be indexed by a class which implements
+com.relevanz.indyo.contenthandler.FileContentHandler (e.g.
+TextHandler, ZIPHandler, etc). Via the datasource, applications can
+also associate a search result object with the object that was indexed
+(or optionally use Peter's SearchBean contribution), for display
+purposes.
To summarize, if you:
-a) Want a way of indexing various sources of data, and even nested datasources (like indexing a HTML file, which spawns a custom datasource, say RemoteHTMLDataSource, for every link it encounters)
-b) Simply want a pluggable system of indexing different types of file content (currently plain text, Zip, Tar, GZip file formats are supported, but writing new file content handlers are easy)
+
+a) Want a way of indexing various sources of data, and even nested
+datasources (like indexing a HTML file, which spawns a custom
+datasource, say RemoteHTMLDataSource, for every link it encounters)
+
+b) Simply want a pluggable system of indexing different types of file
+content (currently plain text, Zip, Tar, GZip file formats are
+supported, but writing new file content handlers are easy)
then Indyo may be worth checking out.
+
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>