Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 86132 invoked by uid 500); 4 May 2001 13:07:39 -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 85812 invoked from network); 4 May 2001 13:07:24 -0000 Message-ID: <3AF2A91C.584CAC89@apache.org> Date: Fri, 04 May 2001 09:05:32 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [c2] sitemap design question (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Donald Ball wrote: > > hey guys. i'm still waiting to see if anyone has a suggestion for how to > do this without using redirects inside xsp. otherwise i'm gonna put > sendRedirect back in the Response object. :) I think there is one side effect that I can't live without: With sendRedirect() out of the picture for the Response object, you can't do it within Actions (which to me is prefered even over the sitemap). I don't like redirects in XSP because we are already sending information down the stream, and there is no guarantee that the sendRedirect() will be successful in XSP (once any information has been sent down the output stream, you cannot invalidate it). I like them in Actions because you are guaranteed not to be sending information to the output stream--so they are safe, and make developing secure apps alot easier. --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org