[Buildbot-devel] XML-RPC

[Steve 'Ashcrow' Milner]

On 29/04/10 17:33 -0700, Dustin J. Mitchell wrote:
>On Thu, Apr 29, 2010 at 5:13 PM, Marc-Antoine Ruel <maruel at chromium.org> wrote:
>> Does anyone uses XML-RPC?
>
>To give some of the background here, in the meeting we discussed
>adding a REST interface to buildbot, and really doing the full design
>there.  My answer was: "ok, we have JSON, XMLRPC, HTML/HTTP, and soon
>direct MySQL for those who use a database backend .. 5 status APIs
>seems a bit much!"
>
>So we're thinking of either removing one of those APIs or merging them
>into the same implementation (e.g., exposing the same methods via JSON
>and XMLRPC).  XMLRPC is the oldest and least featureful, and thus
>first on the chopping block.
>
>For myself, I was recently playing around with a JavaScript frontend
>to alert me to a finished build at Zmanda, and I ended up doing a good
>bit of work to document the XMLRPC interface; what little
>documentation was available before was mostly incorrect.  So I suspect
>it's little-used.
>
>Dustin

I'm all for using JSON via a REST interface. Though, to be honest, as
long as it isn't SOAP I'm happy :-D.

-- 
kthxbye!
Steve 'Ashcrow' Milner
Agent of Infosec
RHCE: https://www.redhat.com/training/certification/verify/?certno=805009277242449
ITIL Foundation: c.721843
IRC: ashcrow
GnuPG ID: 28DFD4BE

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/IT/MU/O d-- s:+> a- C+++$ UBL+++$ P++@ L+++$>++++ !E--> W+++$ !N-
!o K--? !w-- !O- M- !V- PS PE+ Y+ PGP+++ t+ !5 !X R tv+ b+>++ DI+ !D-
G e h !r>+++ y?
------END GEEK CODE BLOCK------

"In the heat of conversation I may have said certain things I believe 
to be untrue. The alleged lie that you might have heard me saying 
allegedly moments ago ... that's a parasite that lives in my neck." 
     -- Tad Ghostal
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://buildbot.net/pipermail/devel/attachments/20100430/3cc8c508/attachment.bin>