«  »

And this is what I ended up with that works:

<%
    params = {"name":"Mr. SOAP"};
    soap.rpc.client ("/radio", "helloWorld", @params, "127.0.0.1", "5335");
%>

---

«  »

OK, another try after help from Dave: Hello Mr. SOAP!

---

«  »

What gives?  Now, I'm getting error messages like "Macro error: Poorly formed XML text, we were expecting a tag. (At character #356.)"  Even in my first test -- which used to work!  And I didn't change and of the code!  Grrr.

---

«  »

OK, I'm stumped.  Here's the code I used:

<%params = {"Mr. SOAP"}; soap.rpc.client ("/radio", "helloWorld", @params, "127.0.0.1", "5335") %>

How do I specify the parameter name?  Is it just in the client code, or do I have to change the code for the procedure?

---

«  »

The previous was the result of testing the new way to write web services in Radio, as Dave revealed here.

It didn't work for me the first few tries.  First because of a stupid typo: I used a ')' instead of a '}', and the visual difference is pretty minimail in this font on this (laptop) screen.  Second, because Radio wouldn't accept an RPC call from 127.0.0.1!  I was stumped until I remembered that I had been playing with the SOAP and XML-RPC pref, and had turned on the feature to allow calls only from specific addresses.  I had entered "192.168." (I still haven't tested if a partial IP will work), and apparently Radio is quit literal: because "127.0.0.1" was on the list, it was blocked.  Understandable behavior, if you think it through.

Now, let's try it again, but this time, using SOAP, instead of XML-RPC: [Macro error: The server, 127.0.0.1, returned a SOAP-ENV:Client fault: Can't call the script "helloWorld" because it doesn't define a parameter named "param1"]

---

«  »

Hello you big lug!

---