[development] module with XML RPC

Khalid B kb at 2bits.com
Thu Aug 31 19:32:42 UTC 2006

If memory serves, it used to be that Drupal's xmlrpc library was adopted
from another project (perhaps the one you pointed to).

There was a rash of xmlrpc security problems in many CMS systems,
including Drupal, so it was decided to rewrite this library in house (I think
it was Dries).

Check the cvs log for that file, it will be better than my memory.

For examples, check the blogapi and drupal modules in core.

On 8/31/06, Augustin (Beginner) <drupal.beginner at wechange.org> wrote:
> Hello,
> I most probably will need to create a new module that needs to handle XML
> RPCalls.
> I have no experience with XML RPC, so I'd like to ask a few general questions
> about Drupal's implementation.
> If I understand well, the files includes/xmlrpc(s).inc are a fork from the
> library:
>  http://scripts.incutio.com/xmlrpc/
> How come the Drupal XML RPC API doesn't use any of the PHP XML RPC functions
> defined here: http://php.net/xmlrpc ?
> Is this a completely different implementation?
> Why?
> Is there a historical/technical reason behind this?
> How does a XML RPC "session" happen?
> During a page load, we can use php to query the DB, get a reply from the SQL
> server, process that reply and display the page according to the reply we
> got.
> Does the procedure happen remotely with XML RPC?
> I.e., if I have a drupal XML RPC client module, that needs to contact a remote
> XML RPC server, do I get a chance to send the call, get the reply and process
> that reply all within one page load, as if it were a SQL query?
> If not, how is the exchange of information handled.
> What modules exist that use XML RPC a lot, that I could study?
> How would a simple code snippet look like? (make a call to server, get reply,
> and have a if / else fork according to the reply we got - or display /
> print_r() the content of the reply).
> I saw a few handbook pages, and some issues about xml rpc, but I can't find
> any information for a total noob...
> Thanks,
> Augustin.

More information about the development mailing list