[NETCONF-1102] Refactor notification stream starts Created: 27/Jul/23  Updated: 08/Nov/23

Status: In Progress
Project: netconf
Component/s: restconf-nb
Affects Version/s: None
Fix Version/s: 7.0.0

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

Issue Links:
Blocks
is blocked by NETCONF-1099 Restore sal-remote create-notificatio... Resolved
Relates
relates to NETCONF-1196 Clean-up RestconfStateStreamsTest class Resolved

 Description   

RestconfStreamsSubscriptionService's path currently overlaps with RestconfDataService, i.e. the access is mediated through delegation. As noted in the current FIXME, the fact we are starting the stream through a GET operation is a REST violation. This harks back to the original implementation which dropped here: https://git.opendaylight.org/gerrit/c/controller/+/5094.

Given that the streams can hold a ton of data, we should start them when the first subscriber attaches and stop them when it detaches.

Current organization of the code deals with updating the datastore, which should actually happen when the stream is created, so this change requires cleaning up component wiring.


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