[Top] [All Lists]

RE: comments on draft-dracinschi-opes-callout-requirements-00

2002-03-20 03:38:52

Responses could be cacheable for just a subset of requests. Example
could be a URL filtering service that returns different responses for
specific groups of users. This becomes an important aspect when looking
at section 3.2.6. If a callout server aggregates multiple responses it
must not only use the earlist expiration, it must also ensure the most
specific caching rule is applied. In some cases there may be situations
where such diverse cacheability rules cannot be contaminated, e.g.
server 1 does language translation and it flags all responses cacheable
per language (as found in the user-agent header). Service 2 does URL
filtering and flags responses be cacheable per LDAP user group. How
should the callout server aggregate this? 

Thanks, Frank

-----Original Message-----
From: owner-ietf-openproxy(_at_)mail(_dot_)imc(_dot_)org 
[mailto:owner-ietf-openproxy(_at_)mail(_dot_)imc(_dot_)org] On Behalf Of 
Markus Hofmann
Sent: Friday, 01. March 2002 21:16
To: Mark Nottingham
Cc: OPES list
Subject: Re: comments on draft-dracinschi-opes-callout-requirements-00

Mark Nottingham wrote:

Perhaps it would be helpful to clarify the interactions between a)
the encapsulated protocol b) the OPES service and c) the callout
protocol. Caching touches all of these in different ways, and that
might be causing the confusion here.

That's a good idea, because there are quite some dependencies between 
the various cachability rules (e.g. the possibly modified response 
from a callout server must NOT be cached longer than indicated in the 
original response from the origin server etc.). We struggeled quite a 
bit ourselves when discussing this, so we need some clear 
considerations here.


<Prev in Thread] Current Thread [Next in Thread>