Random photo
Loading...
Domains for sale
|
June 24, 2004Efficient subtree transformation with SubtreeXPathNavigatorDaniel implemented SubtreeXPathNavigator I was talking about. That's a way cool stuff, I really like it. Now I'm not sure about XmlNodeNavigator - do we need it in Mvp.Xml library or we better remove it to not confuse users with different forms of the same navigator? I feel a bit guilty about Mvp.Xml project and the June plans I announced. Sorry, I just did nothing. I'm way busy with another unexpected stuff I just had to finish first. June 24, 2004 10:57 AM
| #XML in .NET
Comments
Twinks - whenever I want to. Posted by: Oleg Tkachenko at September 22, 2004 1:50 PMYup, I guess I'll try inheriting it from the SubtreeXPathNavigator and see how to handle the differences... Posted by: Daniel Cazzulino at June 29, 2004 4:07 AMI think the right thing would be to have wrapper/helper method/whatever to avoid duplication of implementation, while preserving the functionality. Posted by: Oleg Tkachenko at June 27, 2004 12:33 PMI believe the XmlNodeNavigator is needed anyway, and that's because of the way the navigator is created from an XmlNode. As you know, it's actually a navigator for the owner document. I'd suggest that we keep all the different stuff we are playing with in the Prototype folder until we decide it is ready for the masses, and then move it up to its own level. You never know if some of the ideas that didn't make it will be useful to others. Posted by: DonXML Demsak at June 24, 2004 2:28 PMPost a comment
Listed below are links to weblogs that reference this post:
High-performance XML (IV): subtree transformations without re-parsing from
Performant XML (IV): subtree transformations without re-parsing from
Performant XML (III): subtree transformations without re-parsing from
Performant XML (III): subtree transformations without re-parsing from
High-performance XML (III): subtree transformations without re-parsing from |