Indeed that is much trickier. For the classes it would be OK as long as different customers don't come up with the same package names. Enforce a toplevel package name per customer and you can permission WEB-INF/classes at the OS level accordingly
For WEB-INF/lib : create per-client-subdirectories here and add them to the classpath (of cocoon or tomcat) .. mind you it's just a thought, I am not sure if this is possible at all Jorg -----Original Message----- From: Ryan Heise [mailto:[EMAIL PROTECTED] Sent: Freitag, 29. August 2003 09:04 To: [EMAIL PROTECTED] Subject: Re: Sharing a cocoon instance to save memory On Fri, Aug 29, 2003 at 07:58:27AM +0100, Jorg Heymans wrote: > I don't know about the techniques of sharing jar files to save memory but > there is basically no immediate need to launch different cocoon instances > for different "customers". In the main sitemap.xmap you put something like > > <map:pipeline> > <map:match pattern="customer/*/**"> > <map:mount uri-prefix="customer/{1}" src="customer/{1}/" > check-reload="yes"/> > </map:match> > </map:pipeline> > > > Each customer would be building his website in the mounted customer > directory on the same instance. Thanks Jorg, Yes, I know about that. But can you tell me how to handle the class files associated with each customer's website? It is a problem if all customers must share the same directory to put their class files. Ryan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
