cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <>
Subject Re: [C2] basic C2 serving questions
Date Tue, 08 May 2001 01:17:53 GMT
On Mon, 7 May 2001, Uli Mayring wrote:

> > > So, *.xml goes to Tomcat, *.html remains with Apache, for example. The
> > > Sitemap would be more useful if it ran inside the webserver.
> >
> > Maybe so, but then we would have to create Cocoon plugins for every web server.
> How about just for Apache? It's your own product (in the sense of Cocoon
> and Apache both being ASF projects), so you might want to have
> interoperability.

we do interoperate with apache httpd. apache httpd can easily be
configured to pass a certain urlspace on to a servlet container (e.g.
tomcat), which invokes cocoon on it.

> > If you know that all your HTML is going to be generated, but all your images
> > are read from disk, you can map "*.html" to Cocoon.  If you wanted to map
> > more things like "*.wap" or "*.vrml", then Cocoon can handle that.  However,
> > you do lose out on some of the cool benefits of Cocoon such as browser type
> > detection so that the same URL can be accessed ("/webbapp/inbox") and it
> > will be rendered automagically in the proper format.
> What do I do, when I know that some of my HTML is static and some is
> generated by Cocoon? I mean, this is not a castle-in-the-sky situation,
> but THE most common real-world scenario. It would be cool if I could use
> the sitemap on the webserver, shall I give you more examples? :)

then just have cocoon set up to serve the rest of the HTML via readers.
it's quite fast.

- donald

Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message