+1
I'm also a bit confused by the cocoon: proto. Isn't there more to it than just forward? The parameters to forward are request attributes correct? You can't add request parameters with server side forward. ----- Original Message ----- From: "Konstantin Piroumian" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 09, 2002 3:47 AM Subject: [PROPOSAL] map:redirect-to vs. map:forward > Hi, team! > > I'd like to propose to add a <map:forward path="" /> node to sitemap. > Behavior should be the same as <map:redirect-to uri="cocoon:/..." />. > As redirect and forward are absolutely different in servlet environment then > it would be better to have separate elements for them. I'd leave > <map:redirect-to /> for real redirects (with 302 status code) and use > <map:forward /> for all internal forwards. > > IMHO, forwarding is more obvious then redirect to 'cocoon:/...' uris and > this will reduce the number of questions in users list about the redirection > and its parameters. Also, I'd like to propose to add parameters support to > <map:forward />: > > <map:forward path="next"> > <map:parameter name="page" value="{page}" /> > </map:forward> > > What do you think? > > -- > Konstantin > _________________________________________ > Konstantin Piroumian > Lead Developer > ICQ#: 2297575 > * Work Tel#: +7 095 795 0520 * 1288 > * More ways to contact me <http://web.icq.com/wwp?Uin=2297575> > i See more about me <http://kot-p.hotbox.ru/> > _________________________________________ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]