[
https://issues.apache.org/jira/browse/QPID-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802509#action_12802509
]
Rajith Attapattu commented on QPID-2343:
----------------------------------------
The second patch was based on comments provided by Rafi - The motivation for
the second patch is to use one map instead of one per each type and also to
allow a particular property to be accessed using more than one type.
Ex. heartbeat is treated as an int value in one codepath while another treats
it as long. The new patch conveniently hides these conversions behind a get
method.
> Provide a consistent naming convention for JMS client properties
> ----------------------------------------------------------------
>
> Key: QPID-2343
> URL: https://issues.apache.org/jira/browse/QPID-2343
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.6
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
> Attachments: QPID-2343.patch, QPID-2343_take2.patch
>
>
> It would be nice if all Qpid clients followed a similar convention for naming
> configuration properties.
> The C++ client currently use the following convention.
> "qpid<dot><property_name>" .
> For starters the JMS client could follow the same strategy. Some of its
> properties are starting with "amqj<dot>" while other are using "qpid<dot>".
> The logical choice would be to use "qpid<dot>" with backwards compatibility
> for old property name.
> The following thread captured the discussion happened on qpid-dev
> http://mail-archives.apache.org/mod_mbox/qpid-dev/201001.mbox/%[email protected]%3e
> The following location will be used to document all the client properties.
> http://cwiki.apache.org/confluence/display/qpid/Qpid+extensions+to+AMQP
> As Robert mentioned all properties should indicate how they are used and
> whether they alter only client internal behaviour, or whether they are passed
> down the wire to the broker which could alter broker behaviour
> Later on it will be added to the documentation being developed in the Qpid
> svn.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
