Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <42492399.7020902@eurodyn.com>
Date: Tue, 29 Mar 2005 12:44:57 +0300
From: Emmanouil Batsis <Emmanouil.Batsis@eurodyn.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7.5) Gecko/20041217
MIME-Version: 1.0
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
Subject: [Configuration] thread safety and performance in enterprize apps
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Hi all,

I was wondering if the list members can help me pin down best practices 
regarding use of Configuration in J2EE apps:

* For read-only XML configurations, how does performance differ between:
       - sharing the same instance (via in the application context or 
JNDI) globally (which classes are better for that?)
       - use one instance per thread/request (threadlocal)
       - instantiate configuration objects "locally"

* How does the above work for read-write configurations?

I'd happily compose a document based on given input (even xdoc, as i 
need to learn that too ;-).

Many thanks,

Manos

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org