Date:  Thu, 21 Mar 2002 07:18:52 +0900
From:  m_seki@mva.biglobe.ne.jp
Subject:  [webricken:65] Re: request attributes and handler creation
To:  webricken@notwork.org
Message-Id:  <m3663qq3w3.wl@edwin.mva.biglobe.ne.jp>
In-Reply-To:  <20020321.052508.50050138.gotoyuzo@kotetsu.does.notwork.org>
References:  <3C97D8FB.8090306@imperitek.com>	<20020320.200956.46637479.gotoyuzo@kotetsu.does.notwork.org>	<3C9871D3.9060405@imperitek.com>	<20020321.052508.50050138.gotoyuzo@kotetsu.does.notwork.org>
X-Mail-Count: 00065


Hello, gotoyuzo.

> How about this way?
> 
>     app = YourApp.new("coreStuff")
>     app.addFunnyOption("foo","bar")
>     app.addFunnyOption("alpha","gamma")
>     app.setZoption("gamma")
>     mount("/z", YourHandler, app)

I did so and wrote the application serveer.

I had misunderstanding at first. WEBrick is not application server
but Web server toolkit.

Servlet model of WEBrick is not it of Java. WEBrick's servlet model 
is the simple thing which associates and invokes URL and an object.
I understand that AbstractServlet of WEBrick is a context generated
for every request. We can write the application server (e.g. session
management, some containers) using this primitive which WEBrick provide.