I think I prefer to tie temporaries to the Request since they shouldn't hang
around after I have used them for display. Sure there's plenty of ways to do it
with the session but it doesn't belong there . It's a nice convenience, drop it
in and forget it. Unless you are planning on reusing Request objects ??
Chuck Esterbrook wrote:
> You could also put it in the session and remove it after you're done.
> Soon we're going to be looking Aquarium and the projects that inspired it
> to see if we can merge in those features and ideas (I think they're related
> to MVC, but don't quote me.) http://aquarium.sourceforge.net
> At 03:46 PM 9/4/00 -0400, Jay Love wrote:
> > >
> >Just put it in the request object, then use the forwardRequestFast method
> >of Application. There are (as of this morning) 2 forwardRequest functions
> >in Application. The standard forwardRequest() creates a totally new
> >environment when it is called, so the only thing that is passed is the
> >Session object, if there is one. The forwqardRequestFast method (which I
> >just committed this morning) doesn't create new request, response or
> >transaction objects, it just uses the original ones. Sounds like that's
> >what you're after.