On Wed, May 14, 2014 at 8:42 AM, Joel M. Halpern <[email protected]> wrote: > Templating is described in the archtiecture document. > However, as I said when i presented the material, this is a topic on which > the authors disagree. > I personally do not think it should be a protocol behavior, and therefore do > not see it as something the model needs to represent. > > The basic idea of templating is to allow the I2RS client to say to the I2RS > agent "I want to set this instance to these values, but for all the things I > don't specify, use this template over here to determine what values to set." > This clearly has power. Equally clearly, it can be done at the client > rather than at the agent. >
Seems like i abused the term "template". I.e it seems to me that would fall under " Default values MUST be possible to specify" - which is described in the wiki. Shouldnt this be a model problem? I will fix the wiki entry and remove it from that sub-section. On the OO class/instances: The motivation is to be able to describe "set blah to RIB instance foo". The concept for abstracting a "factory" which is essentially a "class" vs an "instance" of that class seems to belong to the model. cheers, jamal _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
