Qpid
  1. Qpid
  2. QPID-2782

QMF: improve the console api for selective filtering of unsolicited V2 indications.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.7
    • Fix Version/s: 0.7
    • Labels:
      None
    • Environment:

      qmf v2

      Description

      by default, a console registers to receive all available unsolicited v2 data and event indications. Augment the console-side "bind*()" api to allow an application more granular control over the set of events and data indications it will receive.

      Specifically:

      Session.bindPackage(<package name string>): adds to the set of data and event indications those data objects and events defined by the named package.
      Session.bindClass( <package name string>, <class name string>): adds data indications from objects of the given package and class to the set of received indications. If the class name string is not supplied (e.g. None), the allow data indications from all objects of any class within the named package.
      Session.bindEvent( <package name string>, <event name string): allows receipt of events defined by the given package and event name. If the even name is not supplied (e.g. None), then allow receipt of all events defined by the named package.
      Session.bindAgent(<vendor string>, <product string>, <instance string>): accept data and event indication from the named agent(s). If the instance string is not supplied, accept indications from all agents of the given vendor and product. If instance and product is not supplied, accept indications from agents of the given vendor.

        Activity

        Hide
        Ken Giusti added a comment -

        Provided more detail in the routing keys so filtering can be done on the broker rather than the client.

        In those cases where the bindings did not offer enough granularity, and for support of old style routing keys (v1), I have added console-side filters for events, object, class, and agent updates (python console).

        Show
        Ken Giusti added a comment - Provided more detail in the routing keys so filtering can be done on the broker rather than the client. In those cases where the bindings did not offer enough granularity, and for support of old style routing keys (v1), I have added console-side filters for events, object, class, and agent updates (python console).

          People

          • Assignee:
            Ken Giusti
            Reporter:
            Ken Giusti
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development