Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3DBE0D24.1090905@verizon.net>
Date: Mon, 28 Oct 2002 23:23:00 -0500
From: Vadim Gritsenko <vadim.gritsenko@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.1) Gecko/20020826
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: CaheValidity & toString()
References: <06F21F6856B6BF4FADEBF2C3BC2D99233C7529@genoa.lumigent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Stephen Ng wrote:

>>PS In the meantime, workaround is to use such System IDs (cocoon:// 
>>URLs) that have same information as a key, because System IDs are not 
>>ignored.
>>    
>>
>
>Is this possible if the difference is only in the query string? 
>

Yes, see SitemapSource.java:

        // create system ID
        this.systemId = queryString == null ?
            "cocoon://" + requestURI :
            "cocoon://" + requestURI + "?" + queryString;


> If so,
>I don't understand enough about the sitemap/aggregation/cocoon protocol
>to see how to do this....
>

Suppose you want to aggregate cacheable.xsp and have it cached for 
different values of 'param'. Then, you need to aggregate it using:

    cocoon://path/cacheable?param=some-value

Instead of just:

    cocoon://path/cacheable

Latter will also work but it has system ID which does not change thus 
content aggregator will re-create response every time param value 
changes (because CA key consist from system IDs)


Vadim


>Thanks,
>
>Steve
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org