Resurrecting an old thread in
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=683184
Martin, Peter and I discussed how the structure of the history folder should look like. Currently there will be one folder for each versioned resource directly under /history. However, this leads to performance problems as described in
http://thread.gmane.org/gmane.comp.jakarta.slide.user/2366
Martin has a patch that does what it is suggested in the above message and the below text contains a possible path to go for 2.1
Looking for comments and opinions.
Oliver
As a short-term solution, I think this is quite reasonable.
Longer term, I see two major problems:
a) we should generally scale better - not doing linear searches, etc. Ideally, the history path done as it currently works shouldn't be a problem (well, unless people do propfinds on the history folder :-). This is obviously a very long-term thing, but we should work slowly towards it.
b) We still (with OR without this change) have the problem that the history implementation is very broken if you're using access control. It's a hard problem (the semantics of full access control across a versioned repository could be difficult to define), but the current approach basically just ignores the ACLs entirely - so anyone can read objects from their history locations (obviously, this requires _finding_ those objects, which isn't easy, but it's not too hard either). I think we really need to think about what solutions we can come up with for this problem.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
