Re: Caching and metainformation

• Mail folder: WWW Talk Jan 94-present
• Next message: Paul Burchard: "Re: Server control over history?"
• Previous message: Peter Flynn: "Re: <draft-ietf-iiir-html-01.txt, .ps> to be deleted."
• Maybe in reply to: Kevin Altis: "Caching and metainformation"
• Reply: Kevin Altis: "Re: Caching and metainformation"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 15 Feb 1994 15:38:44 --100
Message-id: <9402151357.AA08820@horizon.gw.umn.edu>
Errors-To: listmaster@www0.cern.ch
Reply-To: burchard@horizon.gw.umn.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Paul Burchard <burchard@horizon.gw.umn.edu>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Caching and metainformation
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 721

altis@ibeam.jf.intel.com (Kevin Altis) writes:
> In the cases of documents that are candidates to cache, we
> need to explicitly state which HTTP metainformation
> "fields" a server needs to send in order for the document
> to be cached correctly.

Could you clarify how this would affect POST forms?  Are you  
suggesting that POST forms will have to include explicit  
metainformation to prevent themselves from being cached (which would  
seem to be undesirable in most cases)?

--------------------------------------------------------------------
Paul Burchard	<burchard@geom.umn.edu>
``I'm still learning how to count backwards from infinity...''
--------------------------------------------------------------------