[5607] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

Re: Holding connections open: an immodest proposal

daemon@ATHENA.MIT.EDU (HALLAM-BAKER Phillip)
Thu Sep 15 07:48:33 1994

Date: Thu, 15 Sep 1994 13:32:13 +0200
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: hallam@dxal18.cern.ch
From: hallam@dxal18.cern.ch (HALLAM-BAKER Phillip)
To: Multiple recipients of list <www-talk@www0.cern.ch>

In article <8688@cernvm.cern.ch> you write:

|>Marc VanHeyningen writes:
|>
|>> The only real alternative anyone has suggested to Content-Length: is
|>> the MIME multipart boundary approach.  It's not clear to me that
|>> that's better, and it sure as heck isn't backward-compatible.
|>
|>Content-Length is fine where the server is reading from file it can stat,
|>but becomes problematic where the response is generated by say a program.
|>
|>Another approach is to use a byte code escape mechanism, e.g.
|>
|>        a)  replace all occurrences of \ by \\ and '\0' by \0
|>        b)  use '\0' not preceded by a \ to denote stream delimiter
|>

There is already such a scheme in SMTP the sequence \cr\lf\.\cr\lf terminates
a stream and is escaped by \cr\lf..\cr\lf.

But it is real uggli bunnies.

--
Phillip M. Hallam-Baker

Not Speaking for anyone else.

home help back first fref pref prev next nref lref last post