We have been working with Slide 2.x for quite some time now and having a lot of success. I would like to know about the semantics of Checkout and Checkin from a security perspective. It looks as though user A can perform a Checkout on a resource and then user B could perform a Checkin against that resource at a later time, resulting in a new version. I looked through the Delta V spec (rfc3253) and could not find anywhere that states that a Checked out resource is locked from other users making changes. If this is the case, then the Checkout method really does nothing more than modify some DAV properties on the resource to indicate that its in a checked-out state.
Can someone comment about the implementation of the Checkout and Checkin methods in Slide and how security is applied, or not. Thanks, - Stan -- To unsubscribe, e-mail: <mailto:slide-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:slide-dev-help@;jakarta.apache.org>
