[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    [jira] [Created] (CONFIGURATION-542) Rework sychronization of configurations
From:       "Oliver Heger (JIRA)" <jira () apache ! org>
Date:       2013-04-30 20:16:15
Message-ID: JIRA.12645513.1367352902701.250335.1367352975673 () arcas
[Download RAW message or body]

Oliver Heger created CONFIGURATION-542:
------------------------------------------

             Summary: Rework sychronization of configurations
                 Key: CONFIGURATION-542
                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-542
             Project: Commons Configuration
          Issue Type: Improvement
            Reporter: Oliver Heger
             Fix For: 2.0


In the original approach configuration objects were not thread-safe. In later \
versions, more and more synchronization was added to support concurrent access to \
configuration properties, even when reloads occurred.

Unfortunately, the current implementation is not very clean and has a lot of \
problems. There a several bug reports related to this topic. Therefore, version 2.0 \
which will break backwards compatibility is a good opportunity to introduce a new \
concept for synchronization.

Of course, the new approach should be easier, cleaner, and customizable. I would also \
like to have an option to avoid synchronization completely if this is not required \
for a specific use case. Maybe a similar pattern as used by the Java collections \
framework can be applied: per default, configurations are not thread-safe, but there \
is an option to add synchronization so that they can be accessed concurrently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]