Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <1753131812.1203272554858.JavaMail.jira@brutus>
Date: Sun, 17 Feb 2008 10:22:34 -0800 (PST)
From: "Emmanuel Bourg (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Updated: (CONFIGURATION-180) Cache DatabaseConfiguration
 values for higher performance
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CONFIGURATION-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bourg updated CONFIGURATION-180:
-----------------------------------------

    Fix Version/s:     (was: 1.6)
                   2.0

> Cache DatabaseConfiguration values for higher performance
> ---------------------------------------------------------
>
>                 Key: CONFIGURATION-180
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-180
>             Project: Commons Configuration
>          Issue Type: Improvement
>            Reporter: Stephen Cooper
>            Assignee: Emmanuel Bourg
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: dbpreload.txt, Enhancement33553.checkstyle.patch, Enhancement33553.patch
>
>
> The DatabaseConfiguration class queries each property as it gets the request for each property.  This is 
> nice for ensuring that you're always up to date, but it doesn't give very good performance in enterprise 
> applications, where the database may not be on the same subnet.
> What we need is the ability to hit the database once, get all the keys/values and then serve up 
> "getString" etc. from that cache.
> I'll be opening a separate enhancement to have a generic Reloading Strategy which could then be 
> applied to this caching DatabaseConfiguration approach.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.