[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sub-tree filtering proposals
At 02:28 PM 6/4/2004, David T. Perkins wrote:
>Hi,
>
>On the subseting, you just need to make sure that there is an error code
>that says that the XPATH might be valid, but the agent implementation
>doesn't support it.
>
>(And, of course, there will be people that will say that subsetting
>must not be allowed, since memory, CPU, and network bandwidth is
>free, and, thus, subsetting require more work to be done in figuring
>out how to take a "perfectly reasonable XPATH specification"
>and splitting it into several XPATH specifications, and combining
>the results.)
How about if you, Glenn, and Wes write up a detailed specification
of the exact Xpath subset a NETCONF agent must support, with
rationale and examples? We need concrete proposals to consider
this approach any further. If nobody's willing to write up a
solution proposal, then the issue is moot.
Andy
>At 02:01 PM 6/4/2004 -0700, Wes Hardaker wrote:
>>>>>>> On Fri, 04 Jun 2004 13:34:55 -0700, Andy Bierman <abierman@cisco.com> said:
>>
>>Andy> 2) An "arbitrary" subset of Xpath isn't likely to be easily supported
>>Andy> by off-the-shelf Xpath tools
>>
>>It's likely most xpath implementations will support the subset you
>>need (as opposed to the worse case of trying to get all xpath
>>implementations to support all the xpath functionality in an
>>interoperable way).
>>
>>vendors that want to only include the minimal part of xpath to reduce
>>size, which I suspect is your point, could quite possibly find the
>>sections of code they don't want and remove it [requires code access
>>or a vendor willing to do the work for you of course]. In general,
>>It's a heck of a lot easier to remove something from something you
>>have too much of than create something for something you don't yet
>>have or don't yet have all of.
>Regards,
>/david t. perkins
--
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/>