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
On Tue, 18 Jan 2005 13:12:06 -, 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
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:
1. What the performance implications are (if any) of having up to 300
contexts in one
On Mon, Jan 17, 2005 at 03:02:28PM -0700, Joel McGraw 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).
Do you really need one context per
On Mon, 17 Jan 2005 15:02:28 -0700, Joel McGraw [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:
1. What the
