Future-proofing/improving XML-RPC requests

devbobo

Hey Guys,

A lot of our 3rd XML-RPC applications rely on the order of parameters as the means of identifying parameters, there is a more robust method by which to make these calls.

Instead of calling smumug.login.withPassword...

<?xml version="1.0"?>
<methodCall>
  <methodName>smugmug.login.withPassword</methodName>
  <params>
    <param>
      <value>
        <string>[insert email address]</string>
      </value>
    </param>
    <param>
      <value>
        <string>[insert password]</string>
      </value>
    </param>
    <param>
      <value>
        <string>1.2.0</string>
      </value>
    </param>
    <param>
      <value>
        <string>[insert api key]</string>
      </value>
    </param>
  </params>
</methodCall>

the request can be made like this...

<?xml version="1.0" encoding="UTF-8"?>
<methodCall>
  <methodName>smugmug.login.withPassword</methodName>
  <params>
    <param>
      <value>
        <struct>
          <member>
            <name>EmailAddress</name>
            <value>
              <string>[insert email address]</string>
            </value>
          </member>
          <member>
            <name>Password</name>
            <value>
              <string>[insert password]</string>
            </value>
          </member>
          <member>
            <name>APIKey</name>
            <value>
              <string>[insert api key]</string>
            </value>
          </member>
        </struct>
      </value>
    </param>
  </params>
</methodCall>

with no reliance on parameter order.

Something to think about

David

Kevin L. Kitchens

devbobo wrote:

Hey Guys,

A lot of our 3rd XML-RPC applications rely on the order of parameters as the means of identifying parameters, there is a more robust method by which to make these calls.

Instead of calling smumug.login.withPassword...

<?xml version="1.0"?>
<methodCall>
  <methodName>smugmug.login.withPassword</methodName>
  <params>
    <param>
      <value>
        <string>[insert email address]</string>
      </value>
    </param>
    <param>
      <value>
        <string>[insert password]</string>
      </value>
    </param>
    <param>
      <value>
        <string>1.2.0</string>
      </value>
    </param>
    <param>
      <value>
        <string>[insert api key]</string>
      </value>
    </param>
  </params>
</methodCall>

the request can be made like this...

<?xml version="1.0" encoding="UTF-8"?>
<methodCall>
  <methodName>smugmug.login.withPassword</methodName>
  <params>
    <param>
      <value>
        <struct>
          <member>
            <name>EmailAddress</name>
            <value>
              <string>[insert email address]</string>
            </value>
          </member>
          <member>
            <name>Password</name>
            <value>
              <string>[insert password]</string>
            </value>
          </member>
          <member>
            <name>APIKey</name>
            <value>
              <string>[insert api key]</string>
            </value>
          </member>
        </struct>
      </value>
    </param>
  </params>
</methodCall>

with no reliance on parameter order.

Something to think about

David

Does anyone have links to sample C# code on how to make these calls in this manner?

Nikolai

I say go struct - just let us know before you hit us with it

devbobo

Nikolai wrote:

I say go struct - just let us know before you hit us with it

Nik,

It's possible to send like this now with no change on our end.

Cheers,

David

Nikolai

devbobo wrote:

Nik,
It's possible to send like this now with no change on our end.
Cheers,
David

Great!
I was planning on some fixup work tonight, so I might as well change this one, too:-)

Nikolai

Nikolai wrote:

Great!
I was planning on some fixup work tonight, so I might as well change this one, too:-)

David,
FWIF S*E v.188 now uses the improved struct format on all the logins.

devbobo

Nikolai wrote:

David,
FWIF S*E v.188 now uses the improved struct format on all the logins.

ok cool

however, structs can be used on all methods calls.