ok, I think I have the answer.
There is only one C2 servlet in existance that takes the calls using Cocoon (.java), sitemap and the remainder of the url path to determine the processing.
Presumably therefore there are several places where the threads will encounter each other in accessing data objects, as there are a few hastables etc placed about for housekeeping? would this have an upper limit on the number of threads that can be pushed through Cocoon and sitemap Manager?
Also I was looking at the reloading, it seems to check for modifications on every request? this seems a bit of an overhead. I've been running resin, and although it has its' pros and cons, it does automatically reload (if everything) if the conf file is changed, without requests having to be made, as does freemarker. Was there any reason for this model?
any thoughts, or if i'm off track,
cheers
John
-----Original Message-----
From: John Waugh [mailto:[EMAIL PROTECTED]]
Sent: 06 July 2001 17:44
To: Cocoon-Users (E-mail)
Subject: Cocoon2 web-app query
I know this might sound like a bit of a dense question but:
how many servlets are running in the cocoon2 example after installation? am i right in thinking there is only 1 servlet CocoonServlet.java that runs, and the content differences are handled by the Cocoon.java and sitemap end onwards, or in fact is there a seprate CocconServlet deployed for each example? I think this is essentially a relationship between CocoonServlet Cocoon and sitemap that i'm not quite understanding,
if anybody could shed some light it would help.
cheers
John
