Uploaded image for project: 'controller'
  1. controller
  2. CONTROLLER-978

Define a NormalizedNode-based notification API & Provide Reference Implementation

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Resolution: Done
    • Post-Helium
    • None
    • mdsal
    • None

    • Operating System: All
      Platform: All

    Description

      Our notification API is still based on Composite nodes, which were deprecated in Helium release. It also has several drawbacks:

      • it is blocking only
      • it does not provide a vehicle to communicate delivery status

      Create a new API, which will address these concerns and implement it.

      Attachments

        Issue Links

          blocks

          Improvement - An improvement or enhancement to an existing feature or task. CONTROLLER-994 Migrate to use new APIs for normalized nodes (also for rpcs, notifications etc.)

          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. CONTROLLER-1019 Milestone: Migration from deprecated YANGTools components to new replacement

          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. CONTROLLER-1094 Binding Broker: Implement and integrate DOMForwardingNotificationBroker

          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. YANGTOOLS-244 Remove CompositeNode and related interfaces

          • Resolved
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              Unassigned Unassigned
              rovarga Robert Varga
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: