Hi,
> it's too early IMO to judge whether a caching hierarchy manager is
> needed or not...
> IMO the only statement that can be made based on your comparison
> is that if the prototype with very limited functionality were slower than
> jackrabbit with a fully implemented feature set, the protoype's architecture
> would probably need to be reconsidered ;)
I agree.
> - security
> - locking
> - scalability (number of concurrent sessions and repository size)
> - transactions
OK, I will then try to implement (prototype) those features now.
> very flat hierarchies
Yes. We do want to solve that, it will affect the architecture, and we
don't have much experience yet how to best solve it. So I guess it's
also one of the features that should be implemented early.
Regards,
Thomas
|