[
https://issues.apache.org/jira/browse/XERCESJ-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055286#comment-13055286
]
Michael Glavassevich edited comment on XERCESJ-1429 at 6/27/11 2:04 AM:
------------------------------------------------------------------------
Some notes from a chat I had with Thiwanka on IRC today:
* The addEventListener() and removeEventListener() methods on the LSParser
should recognize "load" (for LSLoadEvents) and "progress" (for
LSProgressEvents) as the event types.
* The frequency that LSProgressEvents are reported is indeed implementation
dependent.
* Computing the totalSize attribute may be challenging. The DOM Level 3
specification allows 0 to be returned from getTotalSize(). I would suggest that
we return 0 for now.
* The current position stored in the LSProgressEvent (returned from
getPosition()) can be obtained from the org.apache.xerces.xni.XMLLocator. In
particular see XMLLocator.getCharacterOffset() which returns the current
character offset in the document.
* May want to start a thread on the j-users to get a sense of how frequent
users would want LSProgressEvents to be reported and whether they would want an
option to control the frequency.
was (Author: mrgla...@ca.ibm.com):
Some notes from a chat I had with Thiwanka on IRC today:
* The addEventListener() and removeEventListener() methods on the LSParser
should recognize "load" (for LSLoadEvents) and "progress" (for
LSProgressEvents) as the event types.
* The frequency that LSProgressEvents are reported is indeed implementation
dependent.
* Computing the totalSize attribute may be challenging. The DOM Level 3
specification allows 0 to be returned from getTotalSize(). I would suggest that
we return 0 for now.
* The current position stored in the LSProgressEvent (returned from
getPosition()) can be obtained from the org.apache.xerces.xni.XMLLocator. In
particular see XMLLocator.getCharacterOffset() which returns the current
character offset in the document.
* May want to start a thread on the j-users to get a sense of how frequent
users would want LSProgressEvents to be reported and whether they would want an
option to control the frequency.
> [GSoC]: Asynchronous LSParser and parseWithContext
> --------------------------------------------------
>
> Key: XERCESJ-1429
> URL: https://issues.apache.org/jira/browse/XERCESJ-1429
> Project: Xerces2-J
> Issue Type: New Feature
> Components: DOM (Level 3 Load & Save)
> Affects Versions: 2.9.1
> Reporter: Michael Glavassevich
> Assignee: Thiwanka Somasiri
> Labels: gsoc2011
>
> The goal of this project is to complete the implementation of the DOM Level 3
> LSParser. Though Xerces has a functional LSParser, there are a couple parts
> of the spec which still need to be implemented. This includes an asynchronous
> [1] version which returns from the parse method immediately and builds the
> DOM tree on another thread as well as parseWithContext [2] which allows a
> document fragment to be parsed and attached to an existing DOM.
> Possible Mentors: Michael Glavassevich
> [1]
> http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/load-save.html#LS-LSParser
> [2]
> http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/load-save.html#LS-LSParser-parseWithContext
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
