[Project_owners] Summer of Code projects
lid2000 at tpg.com.au
Sun Jun 5 16:59:59 EDT 2005
I've had nothing but problems using it (version that ships with
Mozilla/Fx at the moment doesn't actually seem to work *at all*, updated
version still has its fair share of problems). I'd like it to not break
horribly when using Unicode characters, not throw exceptions when things
don't exist (even if you're using try/catch), have more control over
request status (ie. abort etc), have a simplified interface (not having
to create objects for everything, you could just throw an array or
integer or string at it (why should I have to create nsIArray objects
then populate them, instead of just sending a plain old JS array?), and
it'd figure out itself the XML code to write, as well as automatically
responses (not sure what the hell it would return for structs though),
put strings inside <![CDATA]> tags, and just *work* 100% of the time,
instead of ~70% of the time (I've had problems where it dies trying to
parse objects from a response saying they don't exist, even though
they're clearly there and syntactically correct).
Anyway that's my bitching done. I've thought about rewriting it all so
it'd do that, but at the moment I've backed out all the XML-RPC code in
Deepest Sender, so it's hard to get motivated.
Axel Hecht wrote:
> Christopher Ottley wrote:
>> David Murray wrote:
>>> Rewrite the XML-RPC component from scratch!
>> Uhm, why? The XML-RPC component works fine. The problem is the latest
>> update of the .js file isn't included in Firefox / Mozilla (at least
>> it wasn't last I checked). For an extension that needed it, I just
>> included it with a different contract ids
>> "@mozilla.org/xml-rpc/client;2" and "@mozilla.org/xml-rpc/fault;2". I
>> can't see why it isn't included as at the time I was using revision
>> 1.5 datetime 2003/07/09 03:42:19.
> The version that will ship with 1.1 is 1.34,
> and the changelog looks like Samuel hasn't been working on that code for
> over a year.
> How about someone picking up stuff on the buglist and submit patches? I
> honestly didn't look, but rewrite or fork are not the answer here. If
> you have problems with landing existing patches, mail drivers at m.o.
> Project_owners mailing list
> Project_owners at mozdev.org
More information about the Project_owners