[development] Continued Services woes

Blake Senftner bsenftner at earthlink.net
Sat Mar 5 14:49:44 UTC 2011


Take a look at this d.o page:


It shows example XMLRPC code for Services 6.x-2.0 (which predates the 6.x-2.2 rewrite) using both with and without API keys. (The example code showing logic with API key authentication is a comment at the bottom.) Perhaps this will provide the comparison info you seek to learn how your parameters need to be handled without authentication. 

bsenftner at earthlink.net

On Mar 4, 2011, at 8:32 PM, jeff at ayendesigns.com wrote:

> Blake, thanks very much for pointing me at these two examples. So, my first question is regarding the packaging of the parameters. In my case, there will be no authentication. How does that affect the creation of a hash, etc.?
> Jeff
> On 03/04/2011 06:42 PM, Blake Senftner wrote:
>> Here's some example code I posed at d.o showing how to communicate between two Drupal 6 sites using Services 2.2 thru 2.4, & the XMLRPC server:
>> http://drupal.org/node/774298
>> you'll want to examine the "send()" routine, which is used to call any xmlrpc method. The example code uses the Drupal API, rather than cURL, as you are attempting to use. However, the key logic you'll want to see is the "send()" routine, which is the handling & packaging of the method arguments before calling the remote method. Your code you show below is incorrect for XMLRPC parameter packaging.
>> Additionally, as an aid for you to convert between the logic I give above and your attempts to use cURL, I have another post at g.o showing how to communicate with a Services 3.0 REST remote API - with two examples: one using cURL and one using the Drupal API. Granted, my second example is for a REST server in Services 3.0, but it demonstrates the cURL handling - you'll just need to translate the first code example's packaging of the method parameters for XMLRPC transport.
>> http://drupal.org/node/1070066

More information about the development mailing list