[
https://issues.apache.org/jira/browse/JCR-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559016#action_12559016
]
Jukka Zitting commented on JCR-1312:
------------------------------------
I'm not convinced that we really have an issue with performance or memory use.
We're already working behind the whole HTTP stack and related network
latencies, so does it really matter if we can shave off a few microseconds or
kilobytes of overhead?
DOM handling is pretty integrated (139 org.w3c.dom imports) with the
jackrabbit-webdav codebase, and replacing that with something else seems like a
major task. IMHO we should have some quantified performance goal (from the
perspective of the WebDAV client) to justify such a change.
> Get rid of DOM for XML support
> ------------------------------
>
> Key: JCR-1312
> URL: https://issues.apache.org/jira/browse/JCR-1312
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-webdav
> Reporter: Felix Meschberger
>
> Currently the web dav library uses Xerces and DOM to parse and create XML
> data. This mechanism is well-known but has two major issues: It is slow and
> it has a big memory footprint. In order to solve these two issues, I suggest
> to drop the use of the W3C DOM in webdav in favor of something easier and
> more straight forward to use.
> One candidate could be (out of my head and based on my bias towards KXml)
> KDOM. See also http://www.kxml.org.ww
> See also JCR-1261 for more discussions on this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
