Yes..but I am doing the RequestDispatcher forwarding method with no
problems.
Think of it this way..at least for us, our web site is identical to an
application. If we wanted, we could write the application as a stand-alone
desktop app, and give it out. For that reason, when you start an application
its the equivalent of opening your browser and typing in the URL. Once your
at the web site (much like once the application is running), you use the
navigation of the app. Thus, in the example of a web-site application, you
wouldn't (or hopefully shouldn't) use the BACK, FORWARD, etc buttons of the
browser. Its as if they are not there. Thus, the URL line should never be
used during the web-site use, and therefore nobody should care about the
actual pages being displayed there. Also, keep in mind a redirect call is 3
times slower than a forward, in terms of connection access. It has to make a
roundtrip back to the browser, then back to the server again. In a Servlet
2.2 app, I don't see a need for the URL line at all once you get to the
site. But thats just me I guess.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christian Sell
> Sent: Friday, September 01, 2000 2:17 AM
> To: Orion-Interest
> Subject: Re: HTTPSession timeouts in SSL environment
>
>
> As far as I remember, there is another difference between
> sendRedirect() and
> RequestDispatcher.forward(). I once tested both alternatives, and I found
> that with forward(), the client never gets to know that he hase
> been sent to
> another page, i.e. the URL does not show, the reload button
> reloads the page
> from where the forward was done, etc. I think I remember there were even
> problems with links on the page..
>
> >
> >The difference between them (sendRedirect and RequestDispatcher) is that
> >sendRedirect sends back to a browser a response that it should redirect
> >its request to another page/site which implies another request will be
> >sent by a browser. On the other hand, RequestDispatcher gives you
> >possibilities to send a request forth and back (no matter how many
> >times) between web components just on the server side rather then
> >forcing to exchange information through the net as in previous case.
> >
> >I'd rather write:
> >
> >if (done == null)
> > getServletContext.getRequestDispatcher(relogin).forward(req, res);
> >
>
>
>
