OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Streaming XML (WAS: More on taming SAX (was Re: [xm

[ Lists Home | Date Index | Thread Index ]

* Karl Waclawek <karl@waclawek.net> [2004-12-27 23:36]:
> Alan Gutierrez wrote:
> >>Alan Gutierrez wrote:
> >
> >
> >>>  In these cases, it doesn't buy me anything to have the whole
> >>>  document in memory, since I'm either assembling some sort of
> >>>  AST, or just responding to events, any state that is build up is
> >>>  application specific.
> >
> >
> >>That is why this whole discussion isn't that interesting to me.
> >
> >
> >    Streaming XML, or the documents verus events debate? I've kind
> >    of found the ins and outs of events to be entertaining.

> I meant that your point about state being app-specific is also my
> experience. So, the problem of how to best build/maintain state
> for streaming transformations is app-specific too and solving it
> in some platform-independent language neutral form just means
> inventing another language (so how is it language independent
> then?) which makes me think: why not use the languages I already
> know.

    The ins and outs that are missing, if I think about it are.

    1) A better way to define an event.
    2) A ready facility to maintain the context of a event.

    What I think I came across is a way to package some of the
    drugdery of SAX using composition, especially the Decorator
    design pattern.

Alan Gutierrez - alan@engrm.com


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS