On Tue, 18 Jan 2005 13:12:06 -0000, Varley, Roger <[EMAIL PROTECTED]> wrote: > > > > For reasons beyond my control, a web application > > (apache/Tomcat/PostgreSQL) that I support will need to be partitioned > > into one context per customer (to support one database per customer). > > I'm wondering: > > > > Do you really need one database per customer? In a similair situation, we > resolved this by adding a "client code" to all our database tables & indexes. > Each customer/client was given their own URL to access the system and a > filter used the incoming url to load a client code into the request headers > before passing the request to a single servlet. >
Obviously, it all depends on the isolation level you want. For example, you can restrict what web applications can do in a multi-"user" environment by using the security manager. -- xxxxxxxxxxxxxxxxxxxxxxxxx Rémy Maucherat Developer & Consultant JBoss Group (Europe) SàRL xxxxxxxxxxxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
