RE: Issue: IS_HREF_A_CHILD_OF_KEEPALIVE

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Jason Crawford
> [...]
> Julian alluded to the possibility of keepalive going away.    FWIW... I
> don't see anything like that listed on the issues list.

The issue is not explicitly on the list, however it is related
to COPY_LIVE_PROPS. 
The issues I have with keepAlive are
a) how does the client know which property is live in the first place?
b) deltaV copy semantics forbid using keepAlive on version properties
c) If the destination is on another server, WebDAV has no means to
   fulfill keepAlive. It is not possible to know if the remote server
   knows the requested live props.
d) Is there any server/client using it? (I have not seen any)

I would propose to 
1) remove keepalive, maybe allow omit
2) change default copy behaviour to _not_ copy live properties

//Stefan

> J.
> 
> ------------------------------ Julian wrote... --------------------
> Hi.
> 
> Currently, RFC2518 says in 12.12.1 [1]:
> 
>    <!ELEMENT keepalive (#PCDATA | href+) >
> 
> So individual properties are identified by "href" (which doesn't 
> make sense
> in the general case).
> 
> So (assuming that propertybehaviour/keepalive isn't dropped anyway), this
> will need to be changed to:
> 
>    <!ELEMENT keepalive (#PCDATA | prop+) >
> 
> where DAV:prop contains property elements.
> 
> Julian
> 
> 
> [1] <http://www.greenbytes.de/tech/webdav/rfc2518.html#ELEMENT_keepalive>
> 
> 
> ------------------------------------------
> Phone: 914-784-7569,   ccjason@us.ibm.com
> 
> 
> 
>

Received on Thursday, 31 January 2002 10:50:12 UTC