On Sat, 8 May 2004, Lachlan Andrew wrote: > there -- it's just a matter of scale. In fact, I'd be perfectly > happy to be subsumed by Clucene, as long as week keep backward > compatibilty with ht://Dig. As you say, the role of ht://Dig > (spidering and user interface) is complementary to that of Clucene.
I believe the CLucene developers are more focused on providing a indexing/searching library that other can build an application with. And given everyones time constraints, it makes more sense long-term to throw in with them and participate. > > The big problem is the amount of work, but all of the options are a > lot of work. I can really only afford to spend a couple of hours a > week on ht://Dig. To be viable, I think we need at least four times It will be no trivial amount of work to convert htdig to use CLucene as the index/search guts.... unless we make the decision that all configuration options related to the current search/index code are eligible for removal... we'll keep the ones we can, change the definitions of some and others will die. If we try and be fully backwards compatible with the current subset of search/index configs... we'll be asking for trouble. I'm subscribed to the CLucene list.. it's quite active and motivated... and they are working on UTF-8 support... which is motivation enough to consider the switch. I do think we should consider releasing 3.2.0 after a bit of profiling... Neal Richter Knowledgebase Developer RightNow Technologies, Inc. Customer Service for Every Web Site Office: 406-522-1485 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
