Hello J�rgen, Pill, Juergen wrote: > > If I understand you right you are not interested in a full blown WebDAV API > for your file system view (e.g. clients performing propPatches etc), but you > want to use WebDAV as an Internet Filesystem.
You're absolutely right. > If yes, you will need to write a Slide store, that reads all properties and > structure information, directly from the hard disc (structure maps to the > directory infos, properties maps to the file attributes). If you are not > using caching, you may modify the file system directly and all changes will > be reflected immediately in your webdav view. You even can modify with the > webdav view and changes are reflected on the file system. > But, the full webdav protocol will not be supported, e.g. locking, more dead > properties, etc. Right. I understand, no versioning and that like - but what kind of caching is useful? time-oriented? means, every xx minutes an update? Another question, how do I configure the access rights on those mapped webdav collections? If all meta-data is read directly from hard disc, it will be stored only in memory, right? So, where do I save the access rights (they may be different from the UNIX access rights)? Inside the database? And now the most interessting question: is there anybody out there, who is willing to implement that special slide store? ;-) thanx a lot, Sebastian -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
