Closed
Bug 15090
Opened 25 years ago
Closed 19 years ago
Make expat an XPCOM component that exposes SAX interfaces
Categories
(Core :: XML, enhancement, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 315826
Future
People
(Reporter: nisheeth_mozilla, Assigned: nisheeth_mozilla)
References
Details
(Keywords: helpwanted)
Attachments
(2 files)
|
Assignee | |
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Accepting bug and setting milestone to M14...
Ccing brad who's making this happen. Go, Brad!
|
||
Comment 1•25 years ago
|
||
|
|
Assignee | |
Comment 2•25 years ago
|
||
Adding vidur to the cc list.
|
|
Assignee | |
Updated•25 years ago
|
Whiteboard: HELP WANTED
|
|
Assignee | |
Comment 3•25 years ago
|
||
Bulk moving all M14 non-beta stopper bugs to M17...
|
||
Updated•25 years ago
|
Keywords: helpwanted
Whiteboard: HELP WANTED
|
||
Comment 4•25 years ago
|
||
This would simplify implementation of XML-RPC greatly. Adding our keyword, so we
don't miss a thing. Adding myself on the CC list.
Keywords: zopestudio
|
|
Assignee | |
Comment 9•24 years ago
|
||
This bug has been marked "future" because the original netscape engineer working
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug,or if it blocks your work in some way
-- please attach your concern to the bug for reconsideration.
Target Milestone: M20 → Future
|
|
||
Comment 10•24 years ago
|
||
For the XML-RPC client component I had to write my own XML Parser in Javascript
because of this, and the Jabber.org team will have to do the same for their
component.
This is unnessecary, redundant work with Expat part of Mozilla, but as it isn't
exposed as a scriptable XPCOM component. We _could_ write a XPCOM scriptable SAX
compliant XML parser in Javascript, as we then would "only" have two XML parsers
in Mozilla, in stead of a whole host, but this still seems to me to be overkill
and a waste of our time.
|
||
Comment 11•24 years ago
|
||
|
|
||
Comment 12•24 years ago
|
||
I've attached a .tar.gz of the start of a SIMPLE sax parser in javascript, it
needs quite a bit of work, but 80% of the most popular use of it is done.
The intention is that this will develop into an XPCOM component that can be
shared minimally between XML-RPC and Jabber, and possibly anything else that
needs to parse chunks of XML or have raw access to the parser and not a DOM.
Also, the correct evolution would be to replace this with an expat-based
component, whenever someone arrives w/ the time and talent to do so :)
|
|
||
Comment 13•24 years ago
|
||
Great! I'll try and integrate it into XML-RPC as a test this week.
|
||
Updated•24 years ago
|
QA Contact: chrisd → petersen
|
||
Updated•22 years ago
|
QA Contact: petersen → rakeshmishra
|
||
Comment 14•22 years ago
|
||
I may have gotten some work done on this:
http://eXPatCOM.mozdev.org
without having known about this bug.
|
|
||
Updated•21 years ago
|
QA Contact: rakeshmishra → ashishbhatt
|
||
Updated•21 years ago
|
Severity: normal → enhancement
Summary: FEATURE: Make expat an XPCOM component that exposes SAX interfaces → Make expat an XPCOM component that exposes SAX interfaces
|
||
Comment 15•19 years ago
|
||
I'm going to mark this duplicate of bug 315826, since that's where the implementation that's now in the trunk happened.
*** This bug has been marked as a duplicate of 315826 ***
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•