> Hi all,
>
> The LockMethod class of webdav client library has 'refreshOpaqueToken' as
> well as 'lockToken' fields.
>
> Below is the code of its generateHeaders(String host, State state) method:
>
> public void generateHeaders(String host, State state) {
> ...
> if (isRefresh()) {
> setHeader("If", "(<" + refreshOpaqueToken + ">)");
> }
> ...
> }
>From what I understand :
> 1. What are the functional difference between lockToken and
> refreshOpaqueToken ? Currently, lockToken contains an opaquelocktoken.
OpaqueLockToken contains the token of the lock you want to refresh.
LockToken contains the lock token read in the response.
It's not really useful to have two member variables, but they serve a
different purpose : one is set before executing the request, and the other
is read after executing it. So I think it makes sense to have two variables
(although we could merge them).
> 2. When is refreshOpaqueToken really set ?
Two seconds ago, never. I just added a new constructor for doing that.
Remy
