Cart
[Home] [By Thread] [By Date] [Recent Entries]
> As David Brownell points out, this could be achieved by having an > xpath-in-DOM implementation that ran on top of your DOM. That way your > xpath expressions could return live DOM nodes and you'd avoid DOM bloat. > Though I'm not sure that such a nicely de-coupled approach would be as > efficient as the messier bloatware implementations that do it all in > one? I very often run into non-rigourous invocations of "DOM bloat". Note that DOM is a very large interface, but there is no reason that implementations have to be large as well. > BTW, I like the factory proposal that you recommended to Lauren Wood to > avoid spec bloat. I wish I could take credit for the excellent idea, but I can't. Leigh Dodds is the scurvy scoundrel in this case. -- Uche Ogbuji FourThought LLC, IT Consultants uche.ogbuji@f... (970)481-0805 Software engineering, project management, Intranets and Extranets http://FourThought.com http://OpenTechnology.org xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To unsubscribe, mailto:majordomo@i... the following message; unsubscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
