- From: Santiago Pericas-Geertsen <Santiago.PericasGeertsen@oracle.com>
- Date: Fri, 26 Aug 2011 13:19:20 -0400
- To: Tatu Saloranta <tsaloranta@gmail.com>
- Cc: Innovimax SARL <innovimax@gmail.com>, Robin Berjon <robin@berjon.com>, public-exi@w3.org
On Aug 26, 2011, at 1:10 PM, Tatu Saloranta wrote: > On Fri, Aug 26, 2011 at 5:18 AM, Innovimax SARL <innovimax@gmail.com> wrote: >> Thanks Robin for spotting this to all the EXI-Fan >> You're very welcome to the group. EXI is indeed a very important part of the >> efficient XML processing stack >> The point here is to help user to think into processing data *directly* in >> XML, instead of mapping/storing/building tree first >> Let's continue this discussion on the xmlperf mailing list > > Isn't this (avoiding of building a tree) what most high-performance > XML tools do anyway.... dom tree is perhaps the biggest performance > drain on overall processing, if one is built. So what's new here? My thoughts exactly. How is this different from processing XML using the existing push/pull models? -- Santiago
Received on Friday, 26 August 2011 17:20:33 UTC