Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 38082 invoked by uid 500); 23 Jan 2002 08:47:41 -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 38071 invoked from network); 23 Jan 2002 08:47:41 -0000 From: "Matthew Langham" To: Subject: AW: [C2] request parameters automatically passed to cocoon:/process sub-pipeline Date: Wed, 23 Jan 2002 09:52:39 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <3C4E7802.9030703@anyware-tech.com> X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 23.01.2002 09:47:52, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 23.01.2002 09:47:53, Serialize complete at 23.01.2002 09:47:53 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Carsten, >> >But, you're right that this is not always wanted, we have some >cases were we don't want to pass the parameters. I'm still thinking >of a good way to indicate this to the procotol, for example by > "cocoon:/DONTPASSPARAMETERS@info.xml" > >If someone sees a good URI scheme for this, I will be very happy >to implement that then! > >Carsten > Couldn't this be a different protocol, e.g. "raw-cocoon:/info.xml" ? << Isn't this the same thing we implemented and then called "cocoonnp:/..."??? :-))) Matthew -- Open Source Group sunShine - Lighting up e:Business ================================================================= Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn Tel:+49-5251-1581-30 mlangham@s-und-n.de - http://www.s-und-n.de ================================================================= -----Ursprungliche Nachricht----- Von: Sylvain Wallez [mailto:sylvain.wallez@anyware-tech.com] Gesendet: Mittwoch, 23. Januar 2002 09:45 An: cocoon-dev@xml.apache.org Betreff: Re: [C2] request parameters automatically passed to cocoon:/process sub-pipeline Carsten Ziegeler wrote: >Stuart Roebuck wrote: > >>I notice that in the latest official release of Cocoon2, if you have two >>sitemap matches like: >> >>> >>> >>> >>> >>> >>> >>and >> >>> >>> >>> >>> >>> >>and you request the page "info.html?param1=aparam¶m2=anotherparam", >>the info.xml match receives the two request parameters as if it has been >>called with "info.xml?param1=aparam¶m2=anotherparam". >> >>For my current work, this is a very helpful feature, but I'm not >>confident >>that it is intentional, and I don't want to build reliance on a >>side-effect of the current implementation, particularly in light of all >>the good work currently going on to improve sitemap processing. >> >>Could someone clarify whether this is expected behaviour. >> >Yes, this is the wanted behaviour, so you can actually rely on it. > >But, you're right that this is not always wanted, we have some >cases were we don't want to pass the parameters. I'm still thinking >of a good way to indicate this to the procotol, for example by > "cocoon:/DONTPASSPARAMETERS@info.xml" > >If someone sees a good URI scheme for this, I will be very happy >to implement that then! > >Carsten > Couldn't this be a different protocol, e.g. "raw-cocoon:/info.xml" ? Sylvain -- Sylvain Wallez Anyware Technologies - http://www.anyware-tech.com --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org