cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay Freeman \(saurik\)" <sau...@saurik.com>
Subject Re: new Request for internal map:redirect-to's?
Date Mon, 18 Aug 2003 18:23:51 GMT
Sonny:

Isn't what you're asking for capable of being done with a <map:read
src="cocoon:/.."/> instead of a <map:redirect-to/>? Or is your actually
usage case more complicated than your examples. I could almost understand
redirect-to trying to simulate what would happen if a Location header _had_
been sent, except doing it more efficiently, and expecting developers to
just read the data from the other file if that's what they wanted.

Sincerely,
Jay Freeman (saurik)
saurik@saurik.com

----- Original Message -----
From: "Sonny Sukumar" <ahimsadesi@hotmail.com>
To: <users@cocoon.apache.org>
Sent: Monday, August 18, 2003 1:16 PM
Subject: Re: new Request for internal map:redirect-to's?


>
> Alright, I tried logging the hash codes of the Request instance within the
> first pipeline, and then in the redirected to pipeline, and the hash codes
> are always different.  Moreover, it doesn't look like HttpRequest
overrides
> the hashCode() method (looking at the Cocoon API docs), so it's probably
> just based on memory location or something.  This is probably a good
> indication that the objects are different (and hence contain different
> info), since the object probably wouldn't be moved just for a redirect.
>
> In any case, it kind of sucks to resort to storing the things in the
session
> that I only want to persist for the duration of the request and then have
to
> delete them.  It seems to me that if request params can be preserved for
an
> internal redirect, then why not request attributes as well?  Of course, I
> might not be seeing some design issue, but it'd be good to know *what* I'm
> not seeing. ;-)
>
> Let me know what you think,
>
> Sonny
>
> >From: Upayavira <uv@upaya.co.uk>
> >Reply-To: users@cocoon.apache.org
> >To: users@cocoon.apache.org
> >Subject: Re: new Request for internal map:redirect-to's?
> >Date: Mon, 18 Aug 2003 11:55:47 +0100
> >
> >Sonny Sukumar wrote:
> >...
> >
> >>Anyhow, with all that said, my original question still stands:  Is a new
> >>Request instance still produced when such an internal redirect is
handled?
> >>  See my sitemap snippet below:
> >>
> >><map:match pattern="someUri">
> >>  <map:action type="some-action"/>
> >>  <map:redirect-to uri="cocoon:/anotherUri"/>
> >></map:match>
> >>
> >><map:match pattern="anotherUri">
> >>  ...
> >></map:match>
> >>
> >>In the "some-action" action, I set a Request attribute, which is gone by
> >>the time "anotherUri" produces output.  I know it is being set properly
> >>since I've logged it and it looks fine.
> >
> >From a cursory look at the code, it seems that the query string should
> >survive, but I'm not so sure about form parameters. Do you use POST or
GET?
> >If you use POST, can you switch to GET and see if it now works?
> >
> >Regards, Upayavira


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


Mime
View raw message