Stefano Mazzocchi <[EMAIL PROTECTED]> writes: > On 5 Dec 2003, at 06:00, Martin Holz wrote: > > The front end of the system is cocoon for display and the > > XML Spy (or any other XML editor) and some special purpose > > tools for editing. The repository was CVS, but it was to technical > > for some authors, so it was replaced by slide/WebDAV. > > Currently there are about 40,000 documents and 18 GB of > > data in the slide repository. > > Let me ask you something: do you use versioning at all in that > repository?
Yes, I use linear versioning. There has been some problems with versioning. Major problem the authors don't use it very much, because there is no intuitive user interface. Also maintenance/admin tools are missing. There were some problems with the old FileContentStore, because it did not support transactions. Without versioning this is a more theoretical issue, because the transaction was rolled back before something was written to the file system. This is not true for a versioned system. Often manual repair was necessary. However since I use Olivers TxFileContentStore, I have not observed any problems. Third issue is a design flaw in slide, when it comes to performance. To add a child to a ObjectNode you must retrieve the parent from NodeStore, add the child and store the parent in NodeStore. There are no methods for changing the parent inside the store. I see no way to make the store operation perform faster than linear to size of the node. But the size of the node is determined by the number of child urls. So adding a new child to a directory which already has lots of children, will be really slow. Unfortunately this is, how uris for version history resources (VHR) are organized in slide. All VHR have a uri like /history/n , where n is a number, which is incremented for each new VHR. I solved the problem by modifying org.apache.slide.webdav.util.UriHandler to create tree like uris for VHRs. Something like this should be considered for slide 2.1. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
