Re: [Vtd-xml-users] update-operation impact, if any?

[Jimmy Z. <cra...@co...>]

Ok, I think the assumption here is that everything happens within
a single process...
but pipelining usually is more broadly defined as passing XML data
across process's boundry (even across the network, e.g. SOA components)
 between mutiple programs... like unix's IPC, in that case, it is usually
not possible to pass a DOM tree around without re-serializing...

----- Original Message ----- 
From: "Tatu Saloranta" <cow...@ya...>
To: "Jimmy Zhang" <cra...@co...>; "Sun, Vanessa" <vs...@am...>; 
<vtd...@li...>
Sent: Monday, July 02, 2007 9:45 AM
Subject: Re: [Vtd-xml-users] update-operation impact, if any?


> --- Jimmy Zhang <cra...@co...> wrote:
>
>> It is not much different from DOM, albeit VTD-XML's
>> more efficient...
>> when you send DOM downstream, still need to
>> serialize...
>> for VTD-XML, you just call XMLModifier's output()...
>
> Not necessarily, more often it's all within a single
> process, the tree model just gets passed. If so, no
> additional serialization or parsing is needed.
>
> I think it is fair to say that different models are
> more optimal for different use cases, and that heavy
> modifications are amongst hardest use cases for
> extractive parsers to implement efficiently (as
> opposed to read-only that is the most optimal).
>
> Regarding original problem -- it is of course possible
> to move from basic DOM to other Java tree
> alternatives. Also, most xml processing overhead might
> not come directly from DOM model itself: it is good to
> profile to see if it might have to do with other
> processing (xslt if it's being used, xpath, naive
> business logic that uses too much traversal).
>
> -+ Tatu +-
>
>
>
>
> ____________________________________________________________________________________
> Sick sense of humor? Visit Yahoo! TV's
> Comedy with an Edge to see what's on, when.
> http://tv.yahoo.com/collections/222
>