Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 55729 invoked from network); 3 Mar 2004 14:49:50 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Mar 2004 14:49:50 -0000 Received: (qmail 61368 invoked by uid 500); 3 Mar 2004 14:49:17 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 61333 invoked by uid 500); 3 Mar 2004 14:49:17 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 61242 invoked from network); 3 Mar 2004 14:49:16 -0000 Received: from unknown (HELO mout.perfora.net) (217.160.230.41) by daedalus.apache.org with SMTP; 3 Mar 2004 14:49:16 -0000 Received: from [217.160.230.50] (helo=smtp.perfora.net) by mout.perfora.net with esmtp (Exim 3.35 #1) id 1AyXgU-0006YM-00 for dev@cocoon.apache.org; Wed, 03 Mar 2004 09:49:18 -0500 Received: from [208.185.179.12] (helo=reverycodes.com) by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1AyXgU-0002wD-00 for dev@cocoon.apache.org; Wed, 03 Mar 2004 09:49:18 -0500 Message-ID: <4045CD42.2090802@reverycodes.com> Date: Wed, 03 Mar 2004 07:19:14 -0500 From: Vadim Gritsenko User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Event caching and CachedSource References: <4045A0DA.8000208@hippo.nl> In-Reply-To: <4045A0DA.8000208@hippo.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Unico Hommes wrote: > Carsten Ziegeler wrote: > >> Unico Hommes wrote: >> >>> I'd also like to change the protocol URL a little bit. Since the >>> timeout parameter will only be applicable to the delay refresher >>> implementation and not to the event aware one I think it would be >>> better to specify it with a query parameter instead. >>> >>> Current syntax: cache://60@main@http://www.apache.org/ >>> Proposed syntax: >>> cache:http://www.apache.org/?cache-expires=60&cache-name=main >>> >>> The protocol:subprotocol syntax is also more in line with well >>> established conventions such as in jdbc for instance. >>> >>> Let me know if you have any objections or comments. >>> >> >> No objections from me, but the parameters must have clear names, >> which means there shouldn't be a conflict. Imagine: >> >> cache:http://www.apache.org/?cache-expires=60&cache-name=main&expires=500 >> >> >> (Dumb example, I know) But what I mean is that the real url/source >> could also have parameters and it must be clear which ones are >> for the cache source and which ones are for the real source, >> so perhaps something like "cocoon-cache..." or perhaps better >> using invalid names like "cocoon:cache=60"? >> > Yeah I had been thinkin along the same lines. I like the colon > notation because it resembles familiar namespace notation. So I'll go > with your latter suggestion. Does it make sense to have it both ways? So, say, you can use either: cache:main:60@http://www.apache.org/ or: cache:@http://www.apache.org/?cache:name=main&cache:expires=60 ? Vadim