On 11/7/13, 3:51 PM, Eric Osborne (eosborne) wrote:
one is OK, and #2 makes the most sense. In any case it's a read-only thing so
it doesn't really matter how it gets done.
Where it gets hairy is when you want to write to the network. The question
that kicked off this thread was along those lines, if I recall. If you want to
get a mutex on the network as a whole y
This is where I differ from what others may want. I would like a
network-wide topology accessible at each node, but I don't think I2RS
needs to enforce a network-wide mutex. Meaning, let me learn about the
network from a node, then me (as an application) can do what is needed
to change the network. I may have to coordinate with other writers (as
is stated IIRC in the architecture) to prevent conflicts from occurring.
Joe
--
Joe Marcus Clarke, CCIE #5384, | |
SCJP, SCSA, SCNA, SCSECA, VCP ||||| |||||
Distinguished Services Engineer ..:|||||||||::|||||||||:..
Phone: +1 (919) 392-2867 c i s c o S y s t e m s
Email: [email protected]
----------------------------------------------------------------------------
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
