Re: What is left after LOCK/UNLOCK on null resource?

> 1. A null resource is locked.

> Q. Should this resource appear as a member
> URI of its parent?

Yes, it should appear.  All versions of the spec say it should.


> IE displays the lock-null
> resource as a directory, which doesn't seem right.

A directory?  At the protocol level?  Or
just in the gui?


> 2. The null resource is unlocked.
> Q. Should there be anything left if no other
> command is issued in between?

rfc2518 says there should be nothing.  rfc2518bis
(new spec) says there should be a resource.


> IE also continues to show the now unlocked resource as
> a directory, but it doesn't act as a collection, e.g.
> you can't create members within it.
rfc2518 does specify some odd lock-null behavior while it's
still locked, but neither protocol specifies any odd
behavior after unlocked.

> I suspect this is as
> a result of the Slide behaviour.
Check at the protocol level to determine what's happening
there.  The gui might just make it look like a directory
even if the protocol is doing something different.


> Any clarifications greatly appreciated.
Let us know what you discover.

J.

Received on Wednesday, 4 September 2002 02:40:38 UTC