[MDSAL-701] Support for atomic registration of diverse DOMNotificationListeners Created: 19/Oct/21  Updated: 16/Jan/24  Resolved: 25/Jun/22

Status: Resolved
Project: mdsal
Component/s: DOM API, DOM runtime
Affects Version/s: None
Fix Version/s: 10.0.0

Type: New Feature Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks MDSAL-702 Add support for listening on multiple... Resolved
Relates
relates to NETCONF-1224 NetconfDeviceNotificationService.regi... Resolved

 Description   

Our current APIs allow a single listener instance to listen on multiple notifications, which is appropriate for a number of use cases we currently cover.

Unfortunately we do not support atomic registrations for multiple listeners to particular notifications. This results in mdsal-binding-dom-adapter having to perform an additional dispatch to support FooListener contract, as once it receives a callback on its DOMNotificationListener, it needs to go back and look up which notification method needs to be invoked.

We could do much better if we offered a way for each subscribed notification type to be dispatched to a corresponding listener – eliminating the need for a secondary lookup.

This would also offer additional flexibility for binding-dom-adapter, as it could efficiently support its users' subscription to multiple notification types in a type-safe manner.


Generated at Wed Feb 07 20:10:38 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.