Return-Path: 
 <cocoon-dev-return-38618-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 36480 invoked by uid 500); 18 Mar 2003 02:51:05 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 36467 invoked from network); 18 Mar 2003 02:51:05 -0000
Received: from out004pub.verizon.net (HELO out004.verizon.net)
 (206.46.170.142)
  by daedalus.apache.org with SMTP; 18 Mar 2003 02:51:05 -0000
Received: from verizon.net ([141.156.47.107]) by out004.verizon.net
          (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP
          id <20030318025114.UJUX7930.out004.verizon.net@verizon.net>
          for <cocoon-dev@xml.apache.org>; Mon, 17 Mar 2003 20:51:14 -0600
Message-ID: <3E76899F.90700@verizon.net>
Date: Mon, 17 Mar 2003 21:51:11 -0500
From: Vadim Gritsenko <vadim.gritsenko@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [proposal] fixing the encoding problems
References: <BA9BEDD6.1691A%pier@betaversion.org>
In-Reply-To: <BA9BEDD6.1691A%pier@betaversion.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from
 [141.156.47.107] at Mon, 17 Mar 2003 20:51:14 -0600
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Pier Fumagalli wrote:
<snip/>

>But there is a problem... Proxies and caches...
>  
>

AFAIK (took a look at spec too ;):

>If, for example, in my corporation there are two guys, one using Windows in
>jp and one using Linux in en_US, if the first guy requests
>"http://www.vnunet.com/", I'll deliver the page the first time in jp,
>encoded in shift_jis (let's not track content-type for a sec).
>

Vary: Content-Encoding


>Now, when the second guy requests the same page, I'd have to send it in
>en_US maybe encoded in iso-8859-1...
>

Vary: Content-Encoding


>But my corporation proxy (or the cocoon cache), will cache the first version
>it hits, so, to both of them, I'll end up serving the same Japanese
>shift_jis content...
>

Now, proxy will have 2 objects as it knows that responses were different.


>Not good... Needs more thinking indeed...
>

:)

PS Worse case schenario is
Vary: *
which effectively disables any caching...


Vadim

>    Pier
>