Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-713

Settle on one prefix for Dispatch names

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      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:

        qpid-dxrouter.conf
        qpid-dxrouterd
        qdstat
        QD_TOOLS_HOME
        dx_ for C symbols
        qdx for AMQP addresses
      

      A mess! I propose one of the following:

        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
      

      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.

      Attachments

        1. consistent-naming.patch
          521 kB
          Justin Ross

        Activity

          People

            tross Ted Ross
            jross Justin Ross
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: