The Joy of SAX Leonidas FegarasSAX的喜悦列奥尼达Fegaras.pptVIP

The Joy of SAX Leonidas Fegaras University of Texas at Arlington fegaras@ / Design Goals Want to build an XQuery engine based entirely on SAX handlers all the way from the points the input documents are read by the SAX parser up to the point the query results are printed This engine should consist of operators that naturally reflect the syntactic structures of XQuery and can be composed into pipelines in the same way the corresponding XQuery structures are composed to form complex queries The XQuery translation should be concise, clean, and completely compositional Even though it cannot compete with transducers for simple XPaths, it should not sacrifice much on performance in terms of memory and computational overhead But, ... it should be able to beat transducers for complex predicates and deeply nested queries Pull-Based Approach Based on iterators: class Iterator { Tuple current(); // current tuple from stream void open (); // open the stream iterator Tuple next (); // get the next tuple from stream boolean eos (); // is this the end of stream? } An iterator reads data from the input stream(s) and delivers data to the output stream Connected through pipelines an iterator (the producer) delivers a stream element to the output only when requested by the next operator in pipeline (the consumer) to deliver one stream element to the output, the producer becomes a consumer by requesting from the previous iterator as many elements as necessary to produce a single element, etc, until the end of stream What is a Tuple? A vector of components: one component for each scoped for-variable has fixed-size at each point in a pipeline (known at compile time) doesnt need to include the variable names A tuple component is the unit of communication between iterators Passing fully constructed XML elements through iterators is a bad idea for a compositional translation initially, we would have to pass the entire document as a tree! The unit of communication should