Are there an examples of how to use this API for NETCONF subscriptions/events?

Open
#32 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api, networking

Research direction

Start by checking the Netconf-Java API against the linked NETCONF event-notifications specification and the sysrepo server behavior. Determine whether subscriptions are supported, then document a working example or clearly define the missing support; the issue names no files or tests to run.

Written by the indexing model from the issue text.

Description

I am looking to use the Netconf client to subscribe to an event. Basically, whenever a field changes in my sysrepo netconf server, I need my client to know about it. I know there is a spec for this:

https://tools.ietf.org/id/draft-ietf-netconf-netconf-event-notifications-05.html

I am wondering if this Netconf-Java API has that ability to subscribe and if there are examples of it? (I am researching it as I write this, but wanted to throw that question out there just in case).

If this ability is not part of netconf-java, what I may do is just create a loop that simply polls the netconf server every N seconds for updates to the wanted field in sysrepo. Would you consider using the same technique?

Dominant language
Java
Stars
90
Forks
64
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Juniper/netconf-java

All issues in Juniper/netconf-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.