Chuck Williams wrote:
Storing content in a Lucene index is a common approach and works well.
I agree that this is the best approach to use initially.
You might also make the API for storing entries pluggable. This is hard
to do well when you only have a single implementation, so at first you
might not make the pluggable API public. Then, once you have a chance
to implement it with, e.g., shell commands calling subversion and/or
Berkeley DB, and have proven that it's a usable API, then make it
public. Or you could simply make it public from the start, and
encourage others to try it and help you evolve it into a useable
extension point.
Cheers,
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
