Elliotte Rusty Harold wrote: > The user should not have to make special requests to get a fully > conformant parser. This should be the default, and it should not be > possible to produce a non-conformant parser. Anything less is a > violation of XML 1.0.
actually that is part of parser documentation, and for example implementation XMLPULL API based on Xerces 2 XNI will by default be XML 1.0 non validating so user will not need to do anything (and trying to use it in "limited" mode and incompatible with full XML 1.0 mode will be simply not supported) > You have convinced me that pull > parsing is a useful model in general, which I was extremely skeptical > of before. However, I remain convinced that the existing parsers in > Java and the XMLPULL API in particular are deeply flawed. Unless you > are willing to reconsider the principles that underlie the design of > XMLPULL, it will not become a suitable API for XML processing. u would say that current implementations are not meeting your requirements ... > >i would like to ask that when making comments about XMLPULL API > >to be precise if it is API that has flaws (this is serious problem!) > >or particular implementation that needs fixing (that i think is > >minor problem). > > > > Noted. However, it seems to me that the flaws in API design and the > flaws in implementation both stem from the same false preconceptions. > In particular: > > 1. XML 1.0 correctness is negotiable > 2. Size and speed are more important than a clean design > > Thus the flaws in the API and the implementations are very closely related. IMHO design of XMLPULL API is very clean and choices were made to balance between easy to use API and good performance _and_ small memory footprint and still allow full XML 1.0 support - so API tries to do quite a lot! ultimately it is up to XMLPULL API users to decide if they like API. however we think about XMLPULL API as a building block on which higher level layers can be built (like supporting push and pull simultaneously - implemented currently with SAX driver or more OO XML pull event oriented API, or lightweight incremental DOM APIs or very efficient data binding impl. or SOAP processors etc.). if we enable all this to happen then i think that we succeeded ... thanks, alek --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
