Angela Schreiber wrote:
...this definitively will cause problems for some clients -- not all
of them keep the lock token, and rely on DAV:lockdiscovery to
re-discover them.
so they rely on a xml entry that is marked with a ?
hm.
Yep.
one possible (easy?) solution would be to keep the
session objects for a while... that would allow to have
access to the same session object through multiple requests,
without having to remember the locktoken.
but i wouldn't want to cache session forever... a client
may die etc...
I would be sufficient to keep the lock *token*, and to re-attach it to
the current session for the purpose of discovering locks (and only that
purpose).
But of course that would only work when all HTTP requests arrive through
the same HTTP server (think clustering).
In general, we have several mismatches between JCR locking and WebDAV
locking. If we can't fix them, we probably should document them.
In this case, the (IMHO) right fix would be to allow a JCR server to
return the lock token even when it is *not* attached to the session (or
to define an alternate way to get hold of the token).
BR, Julian
