Index: [Article Count Order] [Thread]

Date:  Wed, 20 Mar 2002 08:26:27 +0900 (JST)
From:  GOTOU Yuuzou <gotoyuzo@notwork.org>
Subject:  [webricken:54] Re: RequestDispatcher (patch)
To:  webricken@notwork.org
Message-Id:  <20020320.082627.128885522.gotoyuzo@kotetsu.does.notwork.org>
In-Reply-To:  <3C967342.6040204@imperitek.com>
References:  <000b01c1ce75$b56fe7f0$85222fc0@sarion.co.jp>	<3C967342.6040204@imperitek.com>
X-Mail-Count: 00054

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. It will be realized by just
calling HTTPServer#service. 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