Jimmy, Really interesting work. I've heard about this idea before, but this is the first implementation I know of. Modulo XML conformance issues (already discussed elsewhere) I can see how this can be useful for certain applications. There is one area, however, that I find it is not elaborated enough on the project page: updates. I see that you list incremental updates, but I haven't found a definition for that. Moreover, I would expect DOM to be much more flexible when it comes to updates, which in way, makes your comparison of VTD-XML and DOM a bit unfair. Analogously, comparing VTD-XML to SAX with a null content handler is not apples-to-apples as VTD-XML is defers some work until the application actually uses the data --which, again, may actually be a good thing for some applications, but maybe less so for others that, for example, bind the entire infoset to programming language objects. To summarize, IMO it may be best to position VTD-XML as a new processing model (which I think you are!), but at the same time be explicit and fair when comparing it with existing processing models. Hope this feedback helps. Nice work! -- Santiago On Feb 13, 2006, at 4:57 PM, Jimmy Zhang wrote:
|
- [ANN] VTD-XML Version 1.5 Released Jimmy Zhang
- Re: [ANN] VTD-XML Version 1.5 Released Joseph Kesselman
- Re: [ANN] VTD-XML Version 1.5 Released Elliotte Harold
- Re: VTD-XML Version 1.5 Released jzhang
- Re: VTD-XML Version 1.5 Released Elliotte Harold
- Re: VTD-XML Version 1.5 Release... Jimmy Zhang
- Re: VTD-XML Version 1.5 Re... Elliotte Harold
- Re: [ANN] VTD-XML Version 1.5 Released Santiago Pericas-Geertsen