[MPEG7AudioEnc-devel] MP7DocumentBuilder vs. MP7Writer
Status: Beta
Brought to you by:
holger_c
From: Holger C. <cry...@ie...> - 2004-05-12 09:01:51
|
Hello MPEG7AudioEnc-Developers! I am currently thinking of creating the XML-tree of the MPEG-7 description as a "org.w3c.dom.Document" and not as a "de.crysandt.xml.XMLNode". Advantages of "org.w3c.dom.Document": The Document has the advantage that it is part of the java implementation. It needs a XML-Parser. But they are included by default (java2 1.4: crimson; java2 1.5: xerces). But it is also possible to use other XML-Parser (set property "org.xml.sax.driver"). I have heard Oracle has its own. With this implementation it is no problem to use this one if the user has any benefit using it. Disadvantages of "org.w3c.dom.Document": When I first started the project, I was not familiar with XML (Now I am an expert ;-) ). So I wrote my own XML-Tree which is faster than the Document but supports much less features. IMHO we should change from "de.crysandt.xml.*" to "org.w3c.dom.*". I can convert the MP7Writer class to MP7DocumentBuilder (I already started). Any comments, suggestions, ...? Please let me (us) know. Regards Holger |