W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1995

Re: Content-Transfer-Encoding "packet"

From: Ian Duncan <id@cc.mcgill.ca>
Date: Tue, 1 Aug 1995 08:17:02 -0400 (EDT)
To: Roy Fielding <fielding@beach.w3.org>
Cc: Harald.T.Alvestrand@uninett.no, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.SOL.3.91.950801080810.11779B-100000@amaretto.cc.mcgill.ca>
On Thu, 27 Jul 1995, Roy Fielding wrote:

> >Note that an almost identical mechanism was proposed for SMTP - I think
> >it is still one of the "draft-ietf-mailext" drafts.
> Yes, I am aware of <draft-ietf-mailext-smtp-binary-07.txt>.  That mechanism
> uses a series of separate messages (each message given a 1*DIGIT length)
> to send the binary data.  In other words, it is a stateful message sequence,
> which is something HTTP doesn't do.  

Could please clarify what you mean by 'series of separate messages' since 
this terminology doesn't fit my understanding of SMTP chunking. The BDAT 
command doesn't in any way change data content in the pipe. It's also 
streamable in the sense that you can have more than on outstanding BDAT 
chunk pending on the connection.

... ian
Received on Tuesday, 1 August 1995 05:13:38 UTC

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