Martin Bjorklund wrote:
yes. Actually, we load the entire configuration data and then apply a filter (easy solution but not performant). Ideally, it should parse the XML schemas to find some matching nodes (or search in a dictionnary built from the schemas), load the configuration data of each matching schemas and finally filter.Cridlig Vincent <cridligv@loria.fr> wrote:I totally agree with your suggestion.I proposed earlier on this list to add a "contexts" element, seebling of "filter", and containing one or more "context" elements (namespace + prefix).Yes, I know. I just hope we get a reply this time!It will be much much more efficient (at least in our Netconf implementation) to find the right XML nodes in the case of such XPath relative expression: "//name"Same here.Moreover, the XPath expressions without prefix are still valid.Do you check all namespaces in this case?
For now, namespaces are not very well handled in our agent because I was waiting for some clarifications on this context problem. Still some work in the pipe...
What about you ? Vincent___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com
-- 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/>