qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Created: (QPID-197) Consistent configuration for C++ and Java brokers.
Date Fri, 15 Dec 2006 15:03:20 GMT
Consistent configuration for C++ and Java brokers.
--------------------------------------------------

                 Key: QPID-197
                 URL: http://issues.apache.org/jira/browse/QPID-197
             Project: Qpid
          Issue Type: Improvement
          Components: C++ Broker, C++ Client, Dot Net Client, Java Broker, Java Client, Java
Common, JMS Compliance
            Reporter: Alan Conway


Define a consistent configuration story between the C++ and Java brokers. 

- Define a common configuration model: naming conventions, type system.
- Define standard configuration settings for features suported in both brokers.
- Define naming conventions to avoid using the same config name with different meanings in
each broker

The brokers will have some language specific settings for things that are different between
the two, but wherever it's reasonable we should define common settings. 

Both brokers will support multiple config formats (e.g. XML, property file, boost config file,
the set of supported formats will be different (e.g. Java properties vs C++ command line args)

The brokers may or may not share a common file format, depending on the solutions adopted
by each. If they do share a common format, it should be possible to identify common vs. language
specific settings so either broker can  use the same config file without being confused by
settings intended for the other.

See also: QPID-104

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message