[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: More on taming SAX (was Re: ANN: Amara XML Toolk

• To: Jeff Rafter <lists@j...>
• Subject: Re: More on taming SAX (was Re: ANN: Amara XML Toolkit 0.9.0)
• From: Alan Gutierrez <alan-xml-dev@e...>
• Date: Sat, 25 Dec 2004 04:40:43 -0500
• Cc: Uche Ogbuji <uche.ogbuji@f...>, xml-dev@l...
• In-reply-to: <41CB11D1.50600@j...>
• Mail-followup-to: Jeff Rafter <lists@j...>,Uche Ogbuji <uche.ogbuji@f...>, xml-dev@l...
• References: <1103757598.10272.67.camel@borgia> <20041223055359.GK25900@s...> <1103791522.4600.68.camel@borgia> <1103792754.4600.81.camel@borgia> <41CB11D1.50600@j...>
• User-agent: Mutt/1.4.1i

* Jeff Rafter <lists@j...> [2004-12-23 13:43]:
> >While on the topic of SAX taming features in Amara, there is also
> >amara.saxtools.xpattern_sax_state_machine, which I didn't even bother
> >mentioning in the announcement (too much to cram in).
> 
> Can you expand on your expansion? As I was reading this I was thinking 
> that in the Java/C# world an interesting approach would be to keep a 
> pseudo DOM stack for the event hierarchy. Maybe something where you keep 
> everything at an ancestral level intact while parsing
> 
> 
> <foo>
>   <bar1>
>     <baz1/>
>     <baz2/>
>   </bar1>
>   <bar2>
>     <baz1>
>       <sub/>
>     </baz1>
>     <baz2>text</baz2>
>   </bar2>
> </foo>
> 
> So when the event stream reached /foo/bar2/baz2/text() you would have 
> the following in a DOM like structure:
> 
>   foo
>     \
>      bar1 (... no children)
>      bar2
>        \
>         baz1 (... no children, just the previous sibling and attrs)
>         baz2 (only the StartTag)
> 
> I am not sure that the preceding siblings would be very useful and have 
> more chances for pathological cases but when I construct mini-trees this 
> is the subset I find handy. It is useful when working with an editor to
> understand the immediate context. Unfortunately by requiring the 
> previous siblings you have to maintain quite a bit more... the whole 
> preceding branch of the tree.

    I have a SAX library (in Java) that keeps the stack around, but
    not the preceeding siblings. It is quite useful.

    It is, actually, very useful to keep a stack around that has a
    hash table for each level of the stack, it allows for the
    devleopment of strategies that are themselves stateless.

    Adding the implied stack goes a long way to make SAX event
    processing a more practical solution for a lot of problems.

--
Alan Gutierrez - alan@e...

• Follow-Ups:
  • Re: More on taming SAX (was Re: ANN: Amara XMLToolkit 0.9.0)
    • From: Uche Ogbuji <uche.ogbuji@f...>

• References:
  • ANN: Amara XML Toolkit 0.9.0
    • From: Uche Ogbuji <uche.ogbuji@f...>
  • Re: ANN: Amara XML Toolkit 0.9.0
    • From: Uche Ogbuji <uche.ogbuji@f...>
  • More on taming SAX (was Re: ANN: Amara XML Toolkit 0.9.0)
    • From: Uche Ogbuji <uche.ogbuji@f...>
  • Re: More on taming SAX (was Re: ANN: Amara XMLToolkit 0.9.0)
    • From: Jeff Rafter <lists@j...>

• Prev by Date: Re: Is there any SteelXML?
• Next by Date: Re: XPath and XPattern (was Re: More on taming SAX)
• Previous by thread: Re: More on taming SAX (was Re: ANN: Amara XMLToolkit 0.9.0)
• Next by thread: Re: More on taming SAX (was Re: ANN: Amara XMLToolkit 0.9.0)
• Index(es):
  • Date
  • Thread