webdav documentation | Ben Bimber | 2010-09-20 09:20 |
Status: Closed | ||
i used webdrive to mount the labkey site root on my laptop. navigating through folders seems a lot more responsive than cases where i've used webDAV shares in the past, which is a good thing. while i think allowing users to directly interact w/ files stored in labkey in a manner comparable to the network shares they are accustomed to is going to be popular and appropriate in certain situations, another part of me also believes this has the potential to be quite dangerous. i have a couple questions: 1. after some minimal testing, it seemed like i had the ability to make folders pretty much wherever i wanted. i am guessing that the logic works something like: if the user has write access to that labkey folder, then they can create subfolders? if that right and can/should there be restrictions on this? how does labkey react if you start creating new folders all over the place? 2. a new feature in labkey is the ability to query files using SQL (see exp.datas table). if i remember correctly, if files are altered using webDAV, labkey should be alerted and reflect these changes (ie. delete/move). is this accurate? what about metadata associated with a file? what happens to that on file move? 3. when i mounted the site root, basically every folder was visible, including those starting w/ period and '@'. is that what's supposed to happen? is there a webDAV flag such that certain directories can be made invisible? while i mounted the site root, obviously we would not do this for most cases. nonetheless, there may be instances where a user would mount one folder that has children, we potentially you'd want to hide the ability to navigate into these children. 4. are many clients allowing users to directly interact with files via webdav in a serious way? thanks. |
||