You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2004/06/14 20:47:01 UTC
DO NOT REPLY [Bug 23461] -
"Memory leak" in xpath evaluations
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=23461>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=23461
"Memory leak" in xpath evaluations
------- Additional Comments From zongaro@ca.ibm.com 2004-06-14 18:46 -------
This behaviour is currently required by the DOM Level 3 XPath API [1,2] - the
API require iterators to listen indefinitely for DOM mutation events, so that
they can set their invalidIteratorState flag to true. This is clearly a bad
idea. I recently submitted a comment [3] against the API for this issue.
[1] http://www.w3.org/TR/2004/NOTE-DOM-Level-3-XPath-
20040226/xpath.html#XPathResult-iterateNext
[2] http://www.w3.org/TR/2004/NOTE-DOM-Level-3-XPath-
20040226/xpath.html#XPathResult-invalid-iterator-state
[3] http://lists.w3.org/Archives/Public/www-dom/2004AprJun/0028.html
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org