-
Notifications
You must be signed in to change notification settings - Fork 0
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
Modifiability of data with in a Template (living templates) #7
Comments
If I understand correctly, this is what I've heard called "Living Templates". That is, the template-association is "live" such that any modification to the template immediately impacts all "consumers" of the template. Yes? |
I dont recall hearing the term "Living Templates". But from your explanation, I think I meant the same requirement. |
That was the term we used at Juniper. It's not one used (yet) in the IETF. I guess it relates to the template association being long-lived (not just applied once). |
Ok. I guess we are inline on this. |
Is another way to say this simply that the template is expanded every time a commit occurs? |
Indeed, it is expanded (in ) every time a commit occurs, because is subject to validation. That said, in some implementations, may be ephemeral. In such cases, the templates are also expanded every time a client gets . So there's two cases when templates may be expanded. |
Requirements
It must be possible to modify the data (i.e add/modify/delete data nodes) defined in an already existing Template irrespective of whether there are references to it or not.
If there are references to the template, then the modified template data should get expanded for all its existing references.
Non-Requirements
None.
The text was updated successfully, but these errors were encountered: