W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1998

Re: Issue: message/http or application/http

From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
Date: Thu, 29 Jan 1998 16:53:27 -0800
To: Jacob Palme <jpalme@dsv.su.se>
Cc: Jim Gettys <jg@pa.dec.com>, http-wg@cuckoo.hpl.hp.com
Message-Id: <9801291654.aa14398@paris.ics.uci.edu>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5320
>E-mail does not permit content-transfer-encoding of a multipart,
>only of individual parts, I believe.

I was only referring to single parts.  The message type has its own
encoding restrictions, which is why it may be more appropriate to
recommend use of "application/http" even though the semantics of
"message/http" seemed like the right choice at the time.

This is actually fairly important, since it determines the most likely
method of performing WebDAV operations via E-mail.  The other advantage
of "application/http" is that it can be defined as a pipeline of requests
or a pipeline of responses.

Received on Thursday, 29 January 1998 17:42:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:22 UTC