From: "Akber Choudhry" <[EMAIL PROTECTED]>
[...]
> Some thoughts from the business battlefront:
>
> There is an "replication of function" all the way from Apache through
> Tomcat to Cocoon.
And a big Tomcat call stack between the VM and Cocoon ;-)
IIRC someone already tried in porting Cocoon and Tomcat in Phoenix; what is
the current state?
Could Cocoon be faster on Phoenix instead of Tomcat?
> Also, where is cocoon with regards to servlet filters. A servlet filter
> implementation of Cocoon will enable business with huge investments in
> servlet/jsp apps to leverage cocoon out of the box. I mean - legacy apps
> with servlets/forwarding, working as is - producing xml consumed by cocoon
> - contributing to actions. etc.
This would mean using Cocoon as a basic XSLT processor, undermining all
possible advantages... IMHO the other way round is much better, having
Cocoon use the result of legacy servlets.
Talking about ServletFilters, why not introduce this concept in Cocoon?
For example, it might enable Cocoon to have the opportunity of gzipping
responses even when it won't run necessarily in Tomcat, since we are
currently relying on it for this purpose.
What do you guys think of enhancing the pipelines with a Filter?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
