Asiri Rathnayake wrote: I think the reason there are issues is that you can't just have a partial webdav implementation. For example without locking you have some applications that will behave weirdly. Also since we are not exposing a "real" disk drive, you might also hit some issues with applications trying to save "temporary" files to the disk. We need to detect the most common ones and handle these in the server memory. I think what you first need to do is write some good tests proving that you are implementing the basic functions properly, including locking (and versioning if it is necessary). One we are sure the basic operation work, then we can look at client compatibility and for this we will need a good logging of the operations sent by the client so that we can understand their behavior. Having a test environment with some webdav server that works well could also be usefull to see the normal list of operations sent by clients. 1a implement tests Compatibility with at least Mac and Windows standard tools is key. We need to be able to edit a document in Notepad or MSWord on Windows and one in OpenOffice on mac. You should have sufficient time to work on this. 1a implement tests 1w july 21th 1b refactor code 1w july 28th 2 implement locking 1w August 5th 3 test and fix compatibility 2w August 19th 4 document 5 implement versioning WDYT ? -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

Asiri Rathnayake wrote: My take: - you should find some webdav client library that you can use in your tests (DavExplorer or SLIDE) and use it to send simple commands to your module. Maybe the developers have better ideas ? -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

Le 14-juil.-08 à 10:23, Asiri Rathnayake a écrit : Asiri, I think webdav client classes are known to be: - highly wished by many (really) - not widespread enough or not mature (e.g. Slides' client seemed to have security issues) Very fine if you can influence the jackrabbit client to actually be wide usage, last I checked it not have a sufficient webDAV client (or server? I don't remember, RMI was haunting then). Please be aware though that WebDAV compliance is sometimes quite hard. At least I know the mod_svn had to work individually for each client to make sure that their auto-commit feature works (and it still doesn't on MacOSX webDAV I think). To my knowledge, the most old-fashioned and beloved client is Cadaver, you may want to make sure this one works at least. paul