You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by je...@apache.org on 2001/10/06 21:58:00 UTC

Re: [Bug 3977] New: - Bugs mostly using copyMethod() and moveMove() over existing files/collections

Long time, no post in slide-dev.

>- Using copyMethod() to copy a file to an existing file path with
>  overwrite flag set to true does not change node last modification
>  date.
>
I guess this should be considered in the server side.
Because the client simply reflects the server-response result.

>- Using copyMethod() to copy a collection to an existing collection path
>  with overwrite flag set to false does nothing but returns true.
>
It's same as above.

>- Using moveMethod() to move a collection to an existing file path with
>  overwrite flag set to true returns true but does nothing.
>
Same as above.

>- Using moveMethod() to move a collection to an existing collection path
>  with overwrite flag set to false returns true but does nothing.
>
Same as above.

>- Using mkcolMethod() with the path of an existing file or collection
>  does nothing but returns true.
>
To solve the problem about interoperability with servers,
I made the method returns true, if the collection aleady exists.
As I know most of compatibility are solved, so it would be easy fixing.

>- UnlockMethod() has a very strange behaviour : A test case using
>  lockMethod() and unlockMethod() on the same session works perfect, but
>  using the two methods in different sessions (logout, login between)
>  that not work at all (unlockMethod() returns false and the lock is
>  still there but returned statusCode is 200)
>
Lock in different sessions was not considered.
Because lock methods in client don't manage lock information and
manipulate only WebDAV resources in memory right now.
So if you want to manipulate lock information, you'd better refresh lock.

>- I don't know if it is a planned feature but I could not find an
>  overwrite flag for the putMethod(). Files are always overwritten.
>
I think it's a feature.  So there isn't overwrite flag.
In some advanced Web servers, each of HTTP methods could be access-controlled.

I hope my comments are helpful.

BTW, I have never looked into WebDAV for several months.
Because I'm not doing WebDAV anymore for my work.  :(
So could be some mistakes.  ^^;


Sung-Gu


Re: [Bug 3977] New: - Bugs mostly using copyMethod() and moveMove() over existing files/collections

Posted by Remy Maucherat <rm...@home.com>.
> Long time, no post in slide-dev.

Welcome back Sung-Gu :)

> >- Using copyMethod() to copy a file to an existing file path with
> >  overwrite flag set to true does not change node last modification
> >  date.
> >
> I guess this should be considered in the server side.
> Because the client simply reflects the server-response result.

Yes indeed.

> >- Using copyMethod() to copy a collection to an existing collection path
> >  with overwrite flag set to false does nothing but returns true.
> >
> It's same as above.
>
> >- Using moveMethod() to move a collection to an existing file path with
> >  overwrite flag set to true returns true but does nothing.
> >
> Same as above.
>
> >- Using moveMethod() to move a collection to an existing collection path
> >  with overwrite flag set to false returns true but does nothing.
> >
> Same as above.

The server should return some special status codes in the three cases
mentioned above.

> >- Using mkcolMethod() with the path of an existing file or collection
> >  does nothing but returns true.
> >
> To solve the problem about interoperability with servers,
> I made the method returns true, if the collection aleady exists.
> As I know most of compatibility are solved, so it would be easy fixing.
>
> >- UnlockMethod() has a very strange behaviour : A test case using
> >  lockMethod() and unlockMethod() on the same session works perfect, but
> >  using the two methods in different sessions (logout, login between)
> >  that not work at all (unlockMethod() returns false and the lock is
> >  still there but returned statusCode is 200)
> >
> Lock in different sessions was not considered.
> Because lock methods in client don't manage lock information and
> manipulate only WebDAV resources in memory right now.
> So if you want to manipulate lock information, you'd better refresh lock.

The Slide client indeed forgets about its locks between sessions, and
doesn't attempt to steal locks (ie, try to get the lock tokens based on the
results of a PROPFIND). Other clients are very aggressive on lock stealing,
though (like DAV Explorer).
Note: The Slide server will obsfucate the lock tokens on the locks you don't
own (so that you can't unlock them).

Remy