Index: [Article Count Order] [Thread]

Date:  Tue, 19 Mar 2002 19:22:11 -0500
From:  David Corbin <dcorbin@imperitek.com>
Subject:  [webricken:55] Re: RequestDispatcher (patch)
To:  webricken@notwork.org
Message-Id:  <3C97D633.1010000@imperitek.com>
References:  <000b01c1ce75$b56fe7f0$85222fc0@sarion.co.jp>	<3C967342.6040204@imperitek.com> <20020320.082627.128885522.gotoyuzo@kotetsu.does.notwork.org>
X-Mail-Count: 00055

GOTOU Yuuzou wrote:

>In message <3C967342.6040204@imperitek.com>,
> `David Corbin <dcorbin@imperitek.com>' wrote:
>
>>a) enables RequestDispatcher to support include/forward.  There is 
>>probably much more than can be done here, like providing support for 
>>POST on the forward.  I'm also sure that there are better ways to manage 
>>the response(s), but I think this will cover the 80% case.
>>
>
>Hmm, RequestDispacher class seems to be overdone
>considering its work. 
>
I'm not sure I understand what you mean by this.  You mean more 
complicated than necessary?

>It will be realized by just
>calling HTTPServer#service. 
>
Today, but it would be possible in the future to have RequestDispatcher 
be 'broader in scope', including forwards to other servers, back to the 
actual web server (if it's running in an "app-server mode), etc.  Then 
RequestDispatcher could have the smarts to do this.

>But apparently, the server
>must be able to be referred from servlets.
>If nobody opposes, I'll to add the method to refer the
>server.
>
>And I think that exception handling is required for
>practical use.  How should Dispatcher behave against
>exceptions?
>
>--
>gotoyuzo
>
>