RE: The Http Facility

> -----Original Message-----
> From: Niclas Hedhman [mailto:[email protected]]
> Sent: Saturday, July 24, 2004 09:14
> To: Avalon Developers List
> Cc: Avalon Users
> Subject: The Http Facility
> Importance: High
> 
> 
> Gang,
> 
> I am working on the HTTP Facility for Merlin, and want to be
introducing
> the
> following changes;
> 
> 1. Having a configuration with <listener> at the 'root' level seems
bound
> to
> create messy config files over time, esp when new configuration
parameters
> are introduced.
> I want us to deprecate (and possibly remove, since it is not yet
released)
> this way and instead use (2).
> 
> 2. Introduce <listeners> as a configuration node, with the above
mentioned
> <listener> nodes under it.
> 
> 3. Introduce
>   <servlets>
>     <servlet>
>
<component>/somecontainer/anothercontainer/mycomponent</component>
>       <url>/my-url</url>
>     <servlet>
>   </servlets>

I would not call these servlets because they are not stict servlets (the
are instead regular component that are capable of handling HTTP servlet
request and response messages).

  <mapping>
    <map>
       <url>/my-url</url>
 
<component>/somecontainer/anothercontainer/mycomponent</component>
    </map>
  </mapping>
       
> The implementation is as straight forward as I could imagine, meaning;
> In DefaultServer.initialize() store these mappings into a map, and
when
> the
> ContainmentModelHandler calls the DefaultServer.register(
ComponentModel
> model ), the component path gets translated prior to registering it to
the
> Jetty server. If there is no defined <url> for a component, the
component
> path is used like before.
> 
> WDYT?


Sounds fine to me.

Cheers, Steve.