Closed
Bug 392845
Opened 17 years ago
Closed 17 years ago
Firefox confvars.sh includes xml-rpc as a default extension
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: roc, Assigned: roc)
References
Details
Attachments
(2 files)
731 bytes,
patch
|
benjamin
:
review+
benjamin
:
review+
|
Details | Diff | Splinter Review |
4.30 KB,
patch
|
benjamin
:
review+
Gavin
:
review+
|
Details | Diff | Splinter Review |
See the patch ... the xml-rpc extension is not being mirrored in hg.mozilla.org/cvs-trunk-mirror, and I think it's not intended to be part of Firefox going forward. Is that right?
Assignee | ||
Comment 1•17 years ago
|
||
Attachment #277355 -
Flags: review?
Assignee | ||
Updated•17 years ago
|
Attachment #277355 -
Flags: review? → review?(benjamin)
Comment 2•17 years ago
|
||
Comment on attachment 277355 [details] [diff] [review] fix r=me for mozilla-central
Attachment #277355 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 3•17 years ago
|
||
So Firefox 3 is going to ship with xml-rpc? I thought we were removing it?
Comment 4•17 years ago
|
||
(In reply to comment #3) > So Firefox 3 is going to ship with xml-rpc? I thought we were removing it? You may be thinking of SOAP/WSDL (bug 332174). But you raise a good point. Sayrer? /be
Comment 5•17 years ago
|
||
I'm sure people actually use the xml-rpc component (the poor souls). It's written in JS, so I don't think it's a big deal either way.
Assignee | ||
Comment 6•17 years ago
|
||
Why hasn't it been imported to Mercurial, then?
Comment 7•17 years ago
|
||
Because we were trying to lighten the load for Mozilla 2. If we think it's ok to keep a JS impl of xml-rpc around, I need an owner (being written in JS doesn't mean you can do without that). And we need evidence that xml-rpc is actually used enough to be worth bundling (that too is not a free ride just because the module in question written in JS). Cc'ing more people for input on whether/when to remove xml-rpc. /be
Comment 8•17 years ago
|
||
Well, I should have said I was sure people used XML-RPC. Not sure that they're using our component. A search on mozilla.dev.extensions shows no hits for xml-rpc. Flock uses their own component: http://cvs-mirror.flock.com/index.cgi/mozilla/browser/components/flock/xmlrpc/ ScribeFire uses a component derived from Flock's code. Those are probably the two most serious XML-RPC users in the Mozilla ecosystem. Let's drop it.
Assignee | ||
Comment 9•17 years ago
|
||
Comment on attachment 277355 [details] [diff] [review] fix Okay then, can I get review to check this into CVS for 1.9?
Attachment #277355 -
Flags: review?(benjamin)
Comment 10•17 years ago
|
||
Comment on attachment 277355 [details] [diff] [review] fix r=me for cvs-trunk as well, then. We should probably post to .planning/.platform with this decision.
Attachment #277355 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 11•17 years ago
|
||
checked in
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 12•17 years ago
|
||
You should also remove nsXmlRpcClient.js and xml-rpc.xpt from browser/installer/windows/packages-static and browser/installer/unix/packages-static , no?
Assignee | ||
Comment 13•17 years ago
|
||
Attachment #279668 -
Flags: review?(benjamin)
Updated•17 years ago
|
Attachment #279668 -
Flags: review+
Updated•17 years ago
|
Attachment #279668 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 14•17 years ago
|
||
checked in
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•