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.

Sign up for GitHub

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

Jump to bottom

Split TransportContentParser in RFC capabilities and other ones. #9

Open
isartcanyameres opened this issue Aug 5, 2013 · 0 comments
Open

Split TransportContentParser in RFC capabilities and other ones. #9

isartcanyameres opened this issue Aug 5, 2013 · 0 comments
Labels
enhancement

Comments

@isartcanyameres
Copy link
Member

The idea is having a default TransportContentParser that is compliant with Netconf RFCs (already have that) and other parsers extending it adding support for other capabilities.

The rational behind this is isolating as much as possible each capability (although they may interact if required) and do not require modification of the lib core to add extra capabilities.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@isartcanyameres