Hi Ludovic,
On Sun, Jul 13, 2008 at 7:03 PM, Ludovic Dubost <ludovic(a)xwiki.org> wrote:
Asiri Rathnayake wrote:
Hi Ludovic,
2008/7/13 Ludovic Dubost <ludovic(a)xwiki.com>om>:
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.
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).
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.
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.
I will look into tomcat and see what i can learn from it.
I have following things on my list,
1a implement tests
1. Refactor the code (modularise) and document
2. Implement Locking / Versionning operations.
4. Test and make sure it works on all platforms.
How should i proceed ? what should be given priority ?
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 ?
Cool, i will update the devs list at least twice per week so that we can
keep track of my progress along the lines of above dead-lines.
Thanks.
- Asiri
Since now i'm familiar with code base and
WebDAV protocol itself, i think
i
can pick up the phase a little, but i strongly
believe it is better to
set
some deadlines (milestones) so that i too can
measure my work.
Thanks.
- Asiri
Ludovic
--
Ludovic Dubost
Blog:
http://blog.ludovic.org/
XWiki:
http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Ludovic Dubost
Blog:
http://blog.ludovic.org/
XWiki:
http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs