> What do we do about 3.2? My vote is to call it 'final', update the > website and move forward. I could do this, and have posted this thought > in the past.. no consensus emerged and I have no desire to be > heavy-handed.
+1 > After having looked at many commercial implementation of search engines > over the past few years and following Nutch a bit.. I am still convinced > that HtDig has plenty of legs. I know what you mean. Every time I look at Nutch I decide to stick with htdig 3.1.6 a little longer. However, UTF-8 support is getting super critical and some time in 2006 I'm going to have to bite the bullet and do something. > My thought process for 4.0 is to get the htdig developers to concentrate > on building an application for web-servers rather than trying to do it all > and maintain the inverted index code... the Lucene community has already > cracked that nut. Neal, are you tracking the Java Lucene dev lists? There's some recent discussion with respect to index interoperability that may be relevant. -Jeff ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ ht://Dig Developer mailing list: htdig-dev@lists.sourceforge.net List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
