There is no such mechanism, to my knowledge. Should I start indexing all of our modules?
Pros: - Users won't have to do their own indexing. - Most users don't know about indexing at all, so they'll suddenly see huge speed improvements and be able to access Lucene syntax searches. - Updated modules will come with updated indexes. Cons: - Larger download size. - Frontends without Lucene support get no improvement, just the bigger d/l size. (Think handhelds.) --Chris Karl Kleinpaste wrote: > Is there a mechanism defined in CLucene, or in Sword's use of CLucene, > for noticing that a module's content has been updated more recently > than its CLucene index? > > It seems as though all that can be done is to compare > modtime(DataPath/) against modtime(DataPath/lucene/) and re-invoke > mkfastmod if the module content is newer. > > _______________________________________________ > sword-devel mailing list: [email protected] > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
