[5700] in www-talk@info.cern.ch
Re: holding connections open: a modest proposal
daemon@ATHENA.MIT.EDU (Chris Lilley, Computer Graphics Un)
Mon Sep 19 10:46:29 1994
Date: Mon, 19 Sep 1994 11:25:23 +0200
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: lilley@v5.cgu.mcc.ac.uk
From: lilley@v5.cgu.mcc.ac.uk (Chris Lilley, Computer Graphics Unit)
To: Multiple recipients of list <www-talk@www0.cern.ch>
> In that case, why not just use 'Content-Transfer-Encoding: binary'
> and require 'Content-Length:' to be accurate?
> 2. Use multipart/* and BINARY encoding, and
> send an accurate content length in the header.
> (2) requires that the server know the content length before
> it begins transmitting.
Stealing from PostScript, where the same situation applies (with the Bounding
Box) when programs are generating the file and writing as they go:
[stuff]
Content-Transfer-Encoding: binary
Content-Length: (atend)
[lots of stuff]
Content-Length: 12345678
Yes I know this raises other problems, it was just a suggestion. Does the
program parsing MIME have to know the length at the beginning? Is it OK to know
it later on, check against how many bytes were recieved, and detect it has got
them all?
--
Chris
