[Webkit-unassigned] [Bug 17353] XMLTokenizer breaks applications (libxml2 global callbacks)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 13 22:15:31 PST 2008


mrowe at apple.com changed:

           What    |Removed                     |Added
                 CC|                            |mrowe at apple.com

------- Comment #1 from mrowe at apple.com  2008-02-13 22:15 PDT -------
The IO callbacks registered by
xmlRegisterInputCallbacks/xmlRegisterOutputCallbacks go onto a global stack of
callbacks that are asked in turn whether they can handle the IO for a given
URL.  The fact that these can only be set globally looks to be a limitation of
libxml2.  The fact that the callbacks are only provided with the URL when asked
whether they can handle the load makes it challenging to have WebCore's
callbacks limit themselves to handling IO for WebCore-related resources.  Not
using WebCore's callbacks when globalDocLoader may reduce the problem a little,
but is unlikely to be safe in a multithreaded application.

What is the failure mode that is occurring in applications?  My reading of the
code suggests that documents may be returned as zero-length if there is no
associated WebCore loader, which I would imagine to be the case for uses of
libxml2 outside WebCore.

Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list