I have been experimenting with the locking mechanism in the new release.
What I have come up with is probably a specification question:
Is the only way to release locks to mention them in a transaction operation?
I had kind of though users would lock a small region using using GetFeaturesWithLock and then only choose to modify a subset of them. It could be I have the wrong work flow in mind.
Jody
What I have come up with is probably a specification question:
Is the only way to release locks to mention them in a transaction operation?
Yes. Well, that and set a low expiry.
I had kind of though users would lock a small region using using
GetFeaturesWithLock and then only choose to modify a subset of them. It
could be I have the wrong work flow in mind.
You can more or less do that. If you do a transaction with
releaseAction=SOME then only the features that were affected are released,
the others will still be locked under the same lockId. I'm not sure if
this is exactly the workflow you have in mind, as I don't think the spec
allows you to continue holding a lock after you do a transaction on it -
you have to reobtain a lock. But I also do not really understand the
work-flow of the spec either, as I've never really tried to use it. There
may be something in the archives of the wfs-dev list, or you could ask
that list directly what the workflow should be.
Chris