Hi,
The code I just commited are just small modifications in Berkeley DB
that enable the use of the new compression code, not the code
itself...
I just saw that the integration of the new compression code is
submitted to a vote. So I won't continue commiting before it's ok!
--On the status of the code:
It is fully functional and I have tested it in several configurations
and large indexes. It has an auto-test feature, that when enabled
checks if each page it compresses can be decompressed back to the
original.
The core compression algorithms have been ready for more than a week
now, and I spent last week and a halve integrating it into the indexer
and cleaning up the codes. The code passes purify without leaks nor
errors.
Concerning HtVectorGeneric: My code relies on this, but
HtVectorGeneric hasn't been checked/reviewed so as to be fully
functional. The features I use work fine, but it certainly needs some
attention before everybody starts using it.
What I suggest is to integrate the compression in this version of
htdig (so my vote is yes), to commit the HtVectorGeneric, but that
people avoid using it before I double check it. (probably next week)
Does this seem ok?
Cheers,
Marcel.
----------------------
Marcel Bosc
ECILA
100 av. du Gal Leclerc
93500 Pantin - France
Tel: 33 1 56 96 10 85
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
