Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 56846 invoked by uid 500); 7 Jan 2002 19:46:34 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 56829 invoked from network); 7 Jan 2002 19:46:29 -0000 From: "Vadim Gritsenko" To: Subject: RE: Allowed Sitemap Constructs Date: Mon, 7 Jan 2002 14:46:11 -0500 Message-ID: <005001c197b3$f7934ad0$0a00a8c0@vgritsenkopc> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Peter Royal [mailto:proyal@managingpartners.com] > > On Monday 07 January 2002 11:33 am, Nicola Ken Barozzi wrote: > > > > Maybe repeating things already said but, now, is there a real semantic need > > of matchers *and* selectors? > > A matcher is nothing more than a selector that operates on the requested URI. Matchers do operate on whatever you want: request parameters, request attributes, session attributes, request headers, cookies, wind direction and boss's attitude. Last two are not written yet though ;) (same holds true for selectors) > You are correct, there is not a great need for the duplication, other than > syntactical sugar, which is nice sometimes. It's not even nice; it is better then nice. There are things out there not possible without selectors. Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org