W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 1997

RE: Distributed Authoring Proposals

From: Yaron Goland <yarong@microsoft.com>
Date: Wed, 26 Mar 1997 11:45:14 -0800
Message-ID: <11352BDEEB92CF119F3F00805F14F485026B72D7@RED-44-MSG.dns.microsoft.com>
To: "'Roy T. Fielding'" <fielding@kiwi.ICS.UCI.EDU>, masinter@parc.xerox.com
Cc: w3c-dist-auth@w3.org
Hum.. its a fine point but I'm beginning to see the light. =) I still
believe that content-nature deals with most problems but it doesn't deal
with the multipart/byte-ranges problem. Sounds like Patch will be coming
back from the dead.

> -----Original Message-----
> From:	Roy T. Fielding [SMTP:fielding@kiwi.ICS.UCI.EDU]
> Sent:	Tuesday, March 25, 1997 11:36 AM
> To:	masinter@parc.xerox.com
> Cc:	w3c-dist-auth@w3.org
> Subject:	Re: Distributed Authoring Proposals 
> >I think in MIME that "message" and "multipart" are treated specially.
> >They're not just "application", they're media type where the sender
> >intends for the recipient to actually unwrap the message. I don't
> think
> >you should *ever* store something as "multpart". Rather, a content
> >negotiated resource is "multpart/alternative", message/http is just
> >another wrapper around the HTTP message as if the wrapper weren't
> there,
> >etc.
> That is true for the MIME recipient, but not for the MIME sender.
> Unlike in MIME, WEBDAV represents the process of establishing on the
> server the content of future sends, and therefore anything that
> might be sent in the future must be acceptable as data and not
> as control actions.
> .....Roy
Received on Wednesday, 26 March 1997 15:15:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:10 UTC