Even though every abstract description of SAX prominently
mentions that SAX is an event-driven interface, very few SAX
applications really -use- SAX for event-driven programming.
Instead, mostly SAX is just a way to save memory while
extracting data from an XML document. However, over
asynchronous channels--such as a socket the produces data
over a long duration--SAX is a wonderfully light-weight
programming technique for parsing incoming messages.
Previous Topic
