[
https://issues.apache.org/jira/browse/QPID-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-5351:
------------------------------
Assignee: Ted Ross
> Settle on one prefix for Dispatch names
> ---------------------------------------
>
> Key: QPID-5351
> URL: https://issues.apache.org/jira/browse/QPID-5351
> Project: Qpid
> Issue Type: Improvement
> Components: Qpid Dispatch
> Reporter: Justin Ross
> Assignee: Ted Ross
> Attachments: consistent-naming.patch
>
>
> When we have a chance to clarify a true connection for our users by
> using a consistent convention, we should. Here's what we have now:
> {noformat}
> qpid-dxrouter.conf
> qpid-dxrouterd
> qdstat
> QD_TOOLS_HOME
> dx_ for C symbols
> qdx for AMQP addresses
> {noformat}
> A mess! I propose one of the following:
> {noformat}
> dxrouterd.conf qdxrouterd.conf qdrouterd.conf
> dxrouterd qdxrouterd qdrouterd
> dxstat qdxstat qdstat
> DX_TOOLS_HOME QDX_TOOLS_HOME QD_TOOLS_HOME
> dx_ for symbols qdx_ for symbols qd_ for symbols
> dx for addresses qdx for addresses qd for addresses
> {noformat}
> Expressed as a rule: where it's sensible to use a short form, always
> use "qd" (or whatever ends up being canonical). Otherwise, spell it
> out: qpid/dispatch.
> A standard prefix also improves command-line discoverability:
> qd[TAB][TAB] shows you all the entrypoints.
> I slightly prefer "qd" because it's the simplest abbreviation of Qpid
> Dispatch. The patch attached here uses it, but I am quite willing to
> supply a new set of patches that use another prefix.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
