cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <dani...@nada.kth.se>
Subject Re: [RT] The environment abstraction, part II
Date Mon, 30 Jan 2006 23:13:08 GMT
Sylvain Wallez skrev:
> Daniel Fagerstrom wrote:
>> Sylvain Wallez skrev:
>> ...
>>> Now Cocoon is much more than a web framework, as we discussed in the 
>>> "necessary mutation" thread:
>>> - a servlet
>>> - a component container
>>> - a controller
>>> - a pipeline engine
>>> - many blocks built on top of one of the above.
>>>
>>> The CocoonBean used by the CLI is actually parallel to the servlet 
>>> and uses the lower-level layers.
>>
>> Right now it is but as I implemented the blocks as servlets rather 
>> than Processors, the CLI need to call the blocks at the servlet level 
>> ratherv than the processor level. So it will not be parallel anymore. 
>> And that will save us a lot of parallel setup code.
> 
> Hmm... this looks really close to a servlet engine, where the request 
> dispatcher gives access to other servlets.

Yes.

> Aren't we reinventing the 
> wheel here?

We are. If there is some servlet engine that separates the servlet 
container part from the http protocol and communication parts, we can 
reuse the container part. Given that the servlet container part has a 
good enough API and is lightweight enough.

/Daniel


Mime
View raw message