Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

capabilies comfirm #165

Closed
RogerYaozhenyu opened this issue Jul 31, 2017 · 1 comment
Closed

capabilies comfirm #165

RogerYaozhenyu opened this issue Jul 31, 2017 · 1 comment

Comments

@RogerYaozhenyu
Copy link

RogerYaozhenyu commented Jul 31, 2017

hi, last year, i asked a question about capbilites about libnetconf2 or libnetconf. detailes pls refer to the link as below:
CESNET/libnetconf#248
Now , i want to confirm that if the capablities whch list below are supported in Netopeer2 now? thanks,
if not support, do you have a roadmap to support in the future?
hope can get your feedback.

:notification
:notification1.1
:confirmed-commit
:confirmed-commit:1.1
:partial-lock
:time:1.0
:yang-library
:yang-push:1.0

@michalvasko
Copy link
Member

Hi,

  • :notification supported,
  • :notification1.1 will be supported once an RFC and not a draft,
  • :confirmed-commit not supported, obsolete,
  • :confirmed-commit:1.1 not supported, but will be in future,
  • :partial-lock not supported, no plans for implementation, but it still may be added in future,
  • :time:1.0 not supported, no plans for implementation, but it still may be added in future,
  • :yang-library supported,
  • :yang-push:1.0 not supported (related more to RESTCONF), no plans for implementation, but still may be added in future.

Regards,
Michal

syyyr pushed a commit to syyyr/netopeer2 that referenced this issue Sep 10, 2020
Fix issue where thread specific data is dereferenced inside the key value destructor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants