RE: Links to latest bis working docs

I agree with Julian.  Since the consensus of the working group
was to reject the Translate header approach (for the reasons
Julian mentions, and others), I believe it should not be introduced
in the revised document, and definitely should not be characterized as an
"interoperable solution".

Cheers,
Geoff

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Tuesday, September 10, 2002 2:37 PM
To: Lisa Dusseault; w3c-dist-auth@w3.org
Subject: RE: Links to latest bis working docs



Just two comments on:

1.1       Source property
The Source property has not had interoperability demonstrated, but messages
to the list support keeping some way of retrieving the source of
dynamically-generated Web pages.  An interoperable solution exists (the
Microsoft Translate header) but has received rejection on the list due to
its lack of support for dynamically-generated resources with multiple source
files.


- the Translate header violates RFC2616 which explicitly says that variant
handling is *not* supposed to switch between "getting the source" and
"executing a script"

- the actual implementation in IIS breaks RFC2616 in that it doesn't list
"Translate" as request header on which the GET result varies.


Regards, Julian


--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
-----Original Message-----
From: w3c-dist-auth-request@w3.org [mailto:w3c-dist-auth-request@w3.org]On
Behalf Of Lisa Dusseault
Sent: Tuesday, September 10, 2002 5:07 PM
To: w3c-dist-auth@w3.org
Cc: joels@microsoft.com
Subject: Links to latest bis working docs


I promised yesterday I'd put up links to the most recent work-in-progress.
http://www.sharemation.com/~milele/public/dav/draft-ietf-webdav-rfc2518bis.d
oc
http://www.sharemation.com/~milele/public/dav/RFC2518%20Changes.doc
Sometime after the Interop, I'll be doing the real formatted draft thing of
course.
Lisa

Received on Tuesday, 10 September 2002 15:26:14 UTC