- From: <gclemm@rational.com>
- Date: 2002年1月31日 12:44:01 -0500
- To: w3c-dist-auth@w3.org
- Message-ID: <3906C56A7BD1F54593344C05BD1374B105B8100F@SUS-MA1IT01>
I do remember a discussion of keepalive going away because it appears not to be implemented (and I certainly support it going away). That is my preferred solution to this issue. In any case "REMOVING_KEEPALIVE" (or some other appropriate name for it) should be on the issues list. Cheers, Geoff -----Original Message----- From: Jason Crawford [mailto:ccjason@us.ibm.com] Sent: Wednesday, January 30, 2002 11:16 PM To: Julian Reschke Cc: w3c-dist-auth@w3.org Subject: Issue: IS_HREF_A_CHILD_OF_KEEPALIVE I've added this to my local copy of the issues list. Anyone want to comment on it? Support? Dissent? Julian alluded to the possibility of keepalive going away. FWIW... I don't see anything like that listed on the issues list. 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 12:45:04 UTC