Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Date: Wed, 4 Nov 2009 17:47:11 +0300
From: Mikhail Kryshen <mikhail@kryshen.net>
To: "Tomcat Developers List" <dev@tomcat.apache.org>
Subject: Re: UserConfig: alternative implementation
Message-Id: <20091104174711.942de906.mikhail@kryshen.net>
In-Reply-To: <96e4b5230911031634x458d45ddreafa855245759dc8@mail.gmail.com>
References: <20091104021624.a063258d.mikhail@kryshen.net>
	<96e4b5230911031634x458d45ddreafa855245759dc8@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 3 Nov 2009 16:34:57 -0800
Costin Manolache <costin@gmail.com> wrote:

> Curious: how does it scale for large number of users, in particular if you
> have NFS homes ?

I use it at a university server with 780 user accounts with home
directories mounted via NFS from distinct file server, user database is
LDAP. Reading the remote user database and checking all home directories
for webapps takes about 100 ms of real time.

Performance for the large number of deployed webapps would likely be the
same as with the original tomcat UserConfig or Host having all the apps
in a single appbase.

> It would be interesting to change this to not init the contexts when tomcat
> starts - just register a handler that would start the context on first
> request.
> Or as a Valve that looks for ~foo and then lookups and start the context for
> that user on demand.

Most contexts will probably start soon anyway since every user would want
to check his/her webapp after it is installed. Then to make this approach
useful some checking for long-ununsed contexts would be required or
periodic tomcat restarts to clean-up. Anyway it would be interesting
thing to implement.

> IMHO this could be a nice feature - but it's a perfect example of thing that
> shouldn't be bundled in tomcat, but
> available as a separate download. And if it used a scheme like /user/foo -
> it may even be possible to implement it as a app+standard filter, with just
> one 'internal API' call to load the context.

For me it's not a problem to support this as a separate package, but
tomcat already have such a thing bundled which is not currently very
useful.

--
Mikhail

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org