RE: Poll for consensus on edit operations

["Rob Enns" <rpe@juniper.net>]

> I still wonder why parsing
>     
> "//chassis/slots/slot[instance-id='3']/ports/port[instance-id='7']"
> 
> is more memory hungry than parsing the following XML fragment:
> 
>     <chassis>
>       <slots>
>         <slot instance-id="3">
>           <port instance-id="7">
>           </port>
>         </slot>
>       </slots>
>     </chassis>

Compared to the current NETCONF proposal, the XPATH specification
requires
significantly more resources (implementation, code space, run time
memory).

I think we are in agreement that the above 2 examples can be parsed with
about the same memory requirement using a straightforward bit of code.

Rob

--
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/>