Hi Deepak, > While reflecting on the discussions, i am asking myself these questions and i > think it will be better if we could capture our thoughts together, as i see > different interpretations. > > 1> Template definition: > Is this client data? meaning explicitly configured by the client? Yes, in my > view
Mostly “yes”, but I also think that it possible for the system to define some templates (i.e., in <system>) that may be referenced by data nodes in <running>. > Where does it reside(Datastore view): As it is explicitly configured, in the > running. of course, there are arguments that a explicit set is not a > requirement for it to be in running, but in this case, as the template is > defined explicitly , i am assuming it to be in running. Mostly agree, modulo previous comment that some templates may be in <system>. > 2> Template validation: in case it is treated as client data, should this not > be validated during definition itself? Of course, if it is under anydata, > this is not possible When in <running>, it is client data, and hence it makes sense to want to validate it when the template is defined (not when it’s used). Unfortunately, to validate templates when defined entails data model specific templates (i.e., not an ‘anydata’), which I don’t support (as a contributor) for the reasons listed in my previous email sent a few minutes ago. > 3> Template expansion: > Where does it reside? In NMDA, we say it is in intended DS, but > what about non-nmda servers? in running? For "use-once templates", they are (by definition) expanded in <running>. For "living templates", NMDA says that they are expanded in <intended>. Which makes sense, but I think requires a little clarification. My view is that they are "expanded in <intended>” *only* for the purpose of validation and for when returning the <intended> datastore’s contents to a client. That said, I do NOT think templates MUST be expanded when <intended> is *applied*, as I hope that backend server logic can create optimized structures to minimize memory usage, increasing cache hits, and improving performance. Regarding non-NMDA servers, I’m unsure if possible or desired. As a contributor, I am happy to let this be an NMDA-only feature (same as with the “system-config” draft). Kent // contributor
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
