As a developer who went through the experience I would like to suggest that the following will make my life easier:
1. Document how to write a Store (thoroughness about the interface would be most appreciated!) The thing that makes Java so easy to develop with is that the class libraries that come with the JRE (and JDK) are very well documented.
2. Document the data structures! In fact, I would very much appreciate calling a method with a descriptive identifier instead of figuring out that I have to put a (String, NodeRevisionNumber) into a Hashtable of latestRevisionNumbers.
3. This may come as a surprise: If there was a high-level interface that abstracted WebDAV with more "raw" operations, such as MOVE and MAKECOL, I would have preferred to write to that interface. As I am implementing a versioning filesystem, I had difficulty with the translation from PUT & MAKECOL into NodeStore.createObject() & ContentStore.createRevisionContent() in terms of knowing what was a file and what was a directory. I implemented this first creating object nodes as 0 length files in our document management system backend. Once I received a request to create an object as a child of this object, I transformed the 0 length file into a folder and then created the sub-child as a 0 length file.. Is there a better way?
+1 on the above list! I'd love to use Slide for the WebDAV layer talking to my own store, but my last two efforts stranded in lack of time as I was trying to reverse-engineer the existing stores to extract the specs from them.
Ty, if your store isn't too complex, I'd love to have a peek to see if I could use it as a starter for my own.
Emile
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
