Re: Multiple objects in a single transaction: Making it more concrete

luotonen@ptsun00.cern.ch (Ari Luotonen)
Errors-To: listmaster@www0.cern.ch
Date: Mon, 11 Apr 1994 22:57:20 --100
Message-id: <9404112055.AA16015@ptsun03.cern.ch>
Errors-To: listmaster@www0.cern.ch
Reply-To: luotonen@ptsun00.cern.ch
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: luotonen@ptsun00.cern.ch (Ari Luotonen)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Multiple objects in a single transaction: Making it more concrete
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 558

> Are there any special considerations for cache servers and other
> innovative HTTP variants not adequately addressed?

Speaking for cern_httpd which is just a kind of client-server hybrid --
whatever works for both clients and servers will work for caching proxy.


> (BTW, as long as we're talking about cache servers, how do cache
> servers handle negotiation of Content-Type?)

Proxy becomes a client that can handle all the formats that the remote
client has Accept:ed, and presents them by wrapping them to MIME and
sending back.

-- Cheers, Ari --