I think we're suffering from terminology clash!  In my experience of XSLT, I
understood that it had no concept of input streams. The XSLT language only
transforms infosets.  It is up to some driver program to get XML data into
the template processor.

I'm using push/pull in the sense of synchronisation or communication
protocols. By "pull" parser I mean that the application remains in control
and actively pulls each token from a stream as it processes the stream
contents.  By "push" parser, I mean that the application sets up callbacks
and hands over control to the parser which pushes data to those callbacks.

Cheers,
            Nat.
________________________________
Dr. Nathaniel Pryce
B13media Ltd.
Studio 3a, Aberdeen Business Centre, 22/24 Highbury Grove, London, N5 2EA
http://www.b13media.com


----- Original Message -----
From: "Tobias Reif" <tobiasreif / pinkjuice.com>
To: "ruby-talk ML" <ruby-talk / ruby-lang.org>
Sent: Tuesday, May 07, 2002 3:49 PM
Subject: Re: REXML and streaming APIs


> Nat Pryce wrote:
>
>
> > A recursive descent parser recursively traverses the input structure.
Its
> > structure and flow of control is defined by the grammar and content of
the
> > input.
>
>
> Yes. And that's what's called push in XSLT, where both push and pull are
>   feasible paradigms.
>
> Push works after the input structure, pull ignores it.
>
> Tobi
>
> --
> http://www.pinkjuice.com/
>