Hi, On 6/18/07, Thomas Mueller <[EMAIL PROTECTED]> wrote:
I am currently thinking about a radical solution (you can call it brainstorming): Store the index in a database. This would probably be slower than Lucene, a big disadvantage. Additionally, store data of all workspaces in the same database, using the same connection. Store versions in the same database. Use one database connection per session. Don't use any caching in Jackrabbit (only the database would cache data). Like this you don't run into problems with transaction rollbacks, you don't need to clean up the index from time to time. The Jackrabbit core would get much simpler. The database would not really need to be a SQL database, but it would need a bit more functionality than the current PersistenceManager.
Optimally I'd like to see Jackrabbit *be* that database; search indexes, caching, transactions and all. The hard part is getting to that state without a major revolution in Jackrabbit internals, so I quite like your line of thinking in that it seems to offer a more evolutionary path towards that goal. :-) BR, Jukka Zitting
