Am Freitag den, 6. September 2002, um 17:38, schrieb [EMAIL PROTECTED]:
> Hi, > > thank for the info but I have a question: > >> -----Original Message----- >> From: Stefan Eissing [mailto:[EMAIL PROTECTED]] >> Sent: Wednesday, September 04, 2002 10:00 AM >> To: Slide Users Mailing List >> Subject: Re: LOCKing a non-existent resouce >> >> >> The next revision of RFC 2518 will change the defined >> behaviour of lock-null resources in the following manner: >> >> http://www.webdav.org/wg/rfcdev/issues.htm item 80 > > I folowed the above link. > In my understanding the next revision of RFC 2518 will > change to: "servers should not allow lock-null resources" > and "keep silent about the behaviour if a server allows it" No, it's a little bit more subtle. See http://lists.w3.org/Archives/Public/w3c-dist-auth/2001JulSep/0107.html The term *lock-null resource* will disappear in the spec. The definition of the LOCK method will allow you to lock an *unmapped* resource (non-existing resource), which behaves just like a zero length plain resource. > >> LOCK on a non-existing URL (where the collection parent >> exists) will create a locked, empty plain resource. The >> resource cannot be changed into a collection. When the lock >> expires, the resource will stay. > > Where do you know this from ? I can not find the place where > this beaviour is specified. See the mail from the given link. That's the propsal the dist-auth list agreed upon. Best Regards, Stefan > Thanks, Olli > > -- > Ceyoniq Technology > > -- > To unsubscribe, e-mail: <mailto:slide-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:slide-user- > [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
