Re: SAX and parallel processing
* Uche Ogbuji <Uche.Ogbuji@f...> [2005-01-01 15:29]: > > On Fri, 2004-12-31 at 18:44 -0500, Alan Gutierrez wrote: > > The characters event is interesting, becuase it is an index into > > the parse buffer (in theory, and on Xerces indeed), but a > > characters evet is only ever at the top of the stack. I only > > ever need one. > > Interestingly enough, this is precisely one of the aspects of > Python/SAX that is incompatible to Java (as I intimated earlier). > in Python/SAX, we decided to go with the (in our opinions) much > less tangled approach of making the parameter from characters > events an actual text object, rather than a set of offsets. > > I know the original SAX idea was optimization, but I do think this is > exactly one of those areas where perhaps (IMO) premature optimization > ends up limiting design evolution, and I also think that it interferes > with the "Simple" part. > > Not a problem in Python/SAX. I've placed the characters event in a Characters object, which will convert to string as part of toString, and cache the result. Both worlds. In my model the data is called a Lexeme, and it is separate from and Event. -- Alan Gutierrez - alan@e...
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format