RE: rfc2518 issue: DEFER_LOCK_NULL_RESOURCES_IN_SPEC

| The current implementations have demonstrated that lock null resources
| are not a basis for interoperability.

This statement has been mentioned several times, in one form or
another, in this thread.  Do you have documentation or test cases
for these interoperability problems?

When I did the initial locknull implementation for mod_dav, it seemed
to me that the notion of a lock-null resource as presented in 2518
was very clear and logical.  On what have implementors disagreed?

It seems to me that we gain more from the work already done and
implemented to clarify, if needed, rather than abandon.

Keith

Received on Monday, 23 July 2001 13:58:25 UTC