14 Jul
2008
14 Jul
'08
8:58 a.m.
Asiri Rathnayake wrote:
Hi Ludovic,
On Sun, Jul 13, 2008 at 7:03 PM, Ludovic Dubost <ludovic(a)xwiki.org> 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
Asiri Rathnayake wrote:
Agreed but i'm kind of not sure what sort of tests they should be. I believe
JUnit testing is not what you meant. Please advice me on this, i'm kind of
not sure what sort of approach i should be taking towards implementing tests
but i agree with you that we should have tests.
Hi Ludovic,
2008/7/13 Ludovic Dubost <ludovic(a)xwiki.com>om>:
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).
Compatibility is going to be the number 1 problem
!
How should we tackle this issue ? I kind of am puzzled why it works like
that and how to go about fixing it.