Are you avoiding tying to a streaming implementation because: 1. streaming is bad or unncessary? 2. it's not clear what the best implementation is? 3. there is vendor politics involved?
I'm asking this openly because I'm new to this and don't know the answer. If the answer is 1, I'd love to learn more about the right way to do things. If the answer is 2, has anyone written up some comparisons that you could point me to to learn more? If the answer is 3, how about creating an "unofficial" area where people can check in their favorite extensions along with some explanation of why they think they are good. For example, it might help people to see ten or so hacks to DOMPrint; they could see how it is done and maybe pick up one that's 60% what they want. It would also help to see someone else's alternative to DOMPrint if there is one. Ideally there'd be an unmoderated ratings and review system, sorta like AlphaWorks, so people could dis ideas that are just plain bad and praise ideas that have merit. > Dean Roddey wrote: > > The 'writing part' might be a little misleading. We don't have any canned > formatter for outputting the XML. There are a number of reasons for this. > Partly its because we don't want to tie our code to any particular > streaming implementation. And, partly its because there are a lot of > different requirements for how XML is output. But, you can pretty easily > rip off the code in the DOMPrint example to dump out a DOM tree. > > Bernd Schwonkel wrote: > ... > May be you can give me a tip were I can get an > example or some hints using Xerces for writing.
