Re: SAX or XML::SAX ?

2000-06-22 Thread Ken MacLeod
Stephen Zander <[EMAIL PROTECTED]> writes: > > "Ken" == Ken MacLeod <[EMAIL PROTECTED]> writes: > Ken> A little background first. SAX modules come in three basic > Ken> flavors, "drivers" which generate SAX events (parsers are > Ken> drivers), "handlers" which consume SAX events

Re: SAX or XML::SAX ?

2000-06-01 Thread Stephen Zander
> "Ken" == Ken MacLeod <[EMAIL PROTECTED]> writes: Ken> A little background first. SAX modules come in three basic Ken> flavors, "drivers" which generate SAX events (parsers are Ken> drivers), "handlers" which consume SAX events (writers and Ken> tree builders are handlers), a

Re: SAX or XML::SAX ?

2000-05-29 Thread Ken MacLeod
[I missed this in an earlier response until Michael's more recent post reminded me of it.] "Eric Bresie" <[EMAIL PROTECTED]> writes: > > So please indicate your preference: > > > > 1) SAX::*::* or SAX*::* > > > > 2) no-sub-types or sub-types > Since SAX = Simple API for XML...should thi

Re: SAX or XML::SAX ?

2000-05-23 Thread Ken MacLeod
Michael Koehne <[EMAIL PROTECTED]> writes: > So the question we have : > > The Java implementation of SAX 2.0 is out, and it improve in some > important concepts as the namespace thing, filters, and document > order. Ken had mad XML::Parser::PerlSAX as a part of his > libxmlperl, provi