In reply to Hiroyuki.

yes, that is a valid concern. There are some things we are working on there.

For the moment though, the template change is not persisted (no wr mem).
so there are some ways to back out.

There is a broader consideration of network state and how that is captured and restored. Do you want to have lots of mini-template changes that need to be accounted for, or do you want to have an uber-template you push that encapsulates the end-state.

The API allows you to do both, just that you have to manage the first approach.

As i mentioned there are some interesting things we are working on here just not ready to share yet.

Adam