You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if you would be open to expanding the capabilities of this library so we can leverage the same YAML binding capabilities over RESTCONF.
This would imply few things:
Another transport which may introduce an extra dependency for a nice HTTP library (e.g. requests)
During init, there won't be a netconf session open, but prepare the transport requirements for the future HTTP requests.
I think it may be easier than it sounds like. But the library and the repository are currently called eznc, which implies netconf, so I understand if you wouldn't be open to an enhancement like that. But I'm thinking there are many nice features to be reused.
I'm looking forward to your thoughts.
Cheers,
-Mircea
The text was updated successfully, but these errors were encountered:
Hi,
I was wondering if you would be open to expanding the capabilities of this library so we can leverage the same YAML binding capabilities over RESTCONF.
This would imply few things:
requests
)I think it may be easier than it sounds like. But the library and the repository are currently called
eznc
, which implies netconf, so I understand if you wouldn't be open to an enhancement like that. But I'm thinking there are many nice features to be reused.I'm looking forward to your thoughts.
Cheers,
-Mircea
The text was updated successfully, but these errors were encountered: