Just dump the HashFiler, it doesn't work right and it's slow anyway
since it still uses a BTree to track keys.
On Friday, August 8, 2003, at 07:46 PM, Vadim Gritsenko wrote:
Kevin O'Neill wrote:
HashFiler seems pretty broken (I ran that stress tests and it locked
up).
It's been marked as depricated, but with no one to maintain it (unless
there is a volunteer out there) I don't see it's issues being
resolved.
I see three way forward:
Scratch it. Move it to scratchpad as an unsupported element.
Fix it. Resolve it's issues (if they are indeed resolvable).
Warnings. Emit a warning level log message for every public method
call
saying this class is depricated and broken, please switch to one of
the
other filers.
Personally I'm scratch +1
There is a fourth option. Ignore it, but that provides no way forward
so I
haven't proposed it.
I don't know the right answer as I have never worked with it :)
Vadim
Kimbro Staken
Software, Consulting and Writing http://www.xmldatabases.org/
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
