Re: copy-config

[Phil Shafer <phil@juniper.net>]

Seems completely reasonable.

Thanks,
 Phil


Martin Bjorklund writes:
>Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> wrote:
>> On Fri, Dec 09, 2005 at 12:17:26PM +0100, Martin Bjorklund wrote:
>> 
>> > The <copy-config> operation takes source and target as parameters.  I
>> > think the order of these is wrong - an implementation needs to buffer
>> > the entire inline config before knowing which target is used.  I
>> > suggest that the order is reversed - target before source.
>> > 
>> > The order is correct for edit-config.
>> > 
>> > (our implementation makes use of this for both edit-config and
>> > copy-config in order to find a small set of diffs to apply to the db)
>> 
>> You start processing an operation before you have completed the
>> parsing of the request message which invokes that operation??
>
>Yes.  No persistent stuff and no side effects of course; it's ok to get
>a parse error or whatever later.
>
>
>/martin
>
>--
>to unsubscribe send a message to netconf-request@ops.ietf.org with
>the word 'unsubscribe' in a single line as the message text body.
>archive: <http://ops.ietf.org/lists/netconf/>

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>