I grabbed the latest htdig3 sources from the CVS tree. I am
willing to merge my changes into htdig3 before I send in
the diffs for review. However, that will take a while since I
started with 3.1.3 and the latest sources in CVS appear to
be structurally different.
Also, what is htdig4? Should I be using htdig3 or htdig4 to do
the merges?
Regards,
/Raj Inamdar
Geoff Hutchison wrote:
> At 2:29 PM -0500 11/29/99, Rajendra Inamdar wrote:
> >interest, I will be happy to post a patch. (Source baseline is
> >htdig-3.1.3)
>
> I think I can speak for everyone when I say we'd love a patch. See
> below for a bit more detail. As far as htdig-3.1.x is concerned,
> patches are generally only limited to bug fixes, so I'd say it's
> probably not going in.
>
> As far as htdig-3.2.0b1 is concerned, we'll have to vote after seeing
> the patch, but if the code is reasonably good, I'd personally give
> both features +1.
>
> > With the first approach, database sizes can become large, resulting
> > in slower searches. The second approach probably will have problems
> > with sorting and pagination.
>
> I'm not entirely sure which is necessarily faster. Granted, for many
> people the current approach of merging multiple DB together wastes
> tons of disk space since they end up with the separate databases AND
> the merged one. But this approach requires fewer database accesses.
>
> > In a way, it is similar to the second approach above, except that
> > the merging of results happens within htsearch itself. Since the
> > merged result list can be sorted and paginated, it avoids problems
> > with a wrapper script.
> >
> > One potential downside is, there may be more (database) files
> > open during the search. The modified htsearch seems to be working
> > satisfactorily.
>
> True, but it's also a bit slower since it has to perform the same
> word lookup multiple times. Nevertheless, I think this would be
> greatly appreciated (and often requested). As I said, if it looks
> good, I'll give it a +1 for 3.2.0b1.
>
> > Implemented support for NNTP protocol to index and search newsgroup
> > articles. With this feature, news:// urls are treated similar to
>
> I'll have to see how this is done against 3.1.x. I'd love to see
> support for this in 3.2.x, so if it looks like we can put your
> protocol support into a Transfer.cc subclass fairly easily, then I
> definitely give it a +1 for 3.2.0b1.
>
> -Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
