On Fri, Mar 06, 2015 at 01:04:34PM -0500, Jeffrey Haas wrote: > > > > Thanks, this all makes sense. So there is a viable mechanism to create > > a sequence of linked edits. The main trade-off, however, between a > > single atomic edit and a sequence of linked edits is who is taking the > > pain to cleanup the mess if things fail in the middle. If you write a > > client, you love the server to do it. If you write a server, you love > > the client to do it. ;-) > > It's all pain, but some component has to deal with it. > > I'm glad that restconf seems to have this situation covered, Andy. Is there > a similar mechanism in netconf that I've missed? If so, this completely > deals with the need for i2rs to have to ask for anything new. :-) >
I think the NETCONF solution is more geared towards a single transaction solution, i.e., you can ship stuff into the candidate datastore and then commit the whole change set in one go. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
