cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <>
Subject Re: error handling !*#%!
Date Wed, 20 Mar 2002 14:04:51 GMT
At 8:01 am -0600 20/3/02, Ivelin Ivanov wrote:
>> So a solution to your problem, Jeremy, may be to increase the response
>> buffer. javax.servlet.ServletResponse allows this through
>> setBufferSize(), but this method doesn't exist on
>> cocoon.environment.Response.
>BTW, playing devil's advocate,
>why in the first place Cocoon hides/wraps the standard HttpRequest,
>HttpResponse and other interfaces from the Servlets API. I would guess that
>many people are used to the Servlets API. As the API evolves (2.4 is not too
>far), Cocoon will have to keep adding additional wrapper methods and
>interfaces to keep up with the API.
>It also makes it a little harder to mix other servlet technologies with
>Cocoon, because of that extra barrier of getting used to the proprietary
>Was there a safety concern that made Cocoon designers make such decision ?

Sorry Ivelin, but I believe this is a FAQ.

In my understanding .... It was decided that this was the best way to
separate Cocoon from the Servlet environment, so Cocoon could be used from
the CLI and embedded in Applications.

Hope this helps

regards Jeremy

   Jeremy Quinn                                           Karma Divers
                                                       webSpace Design
                                            HyperMedia Research Centre

   <>     		 <>
   <phone:+44.[0].20.7737.6831>             <>

To unsubscribe, e-mail:
For additional commands, email:

View raw message