?

Log in

No account? Create an account
Having problems with XMLRPC getchallenge - LiveJournal Client Discussions — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Having problems with XMLRPC getchallenge [Jan. 4th, 2005|01:17 am]
LiveJournal Client Discussions

lj_clients

[thewerewolf]
I'm writing an LJ library and client for .NET. My goal is to make the library as easy to use as possible.

I'm creating the XML by hand, posting it via System.Net.WebClient, which is an HTTP client class and has worked perfectly for all the other web access tools I've written - so I'm fairly sure it's not screwing anything up, and I've looked at the headers with a packet sniffer and they look right.

Here's the XML I generate and send:

<?xml version="1.0"?>
<methodCall>
<methodName>LJ.XMLRPC.getchallenge</methodName>
<params>
<param>

</param>
</params>
</methodCall>

But I get this response:

<?xml version="1.0" encoding="UTF-8"?><methodResponse><fault><value><struct><member><name>faultString</name><value><string>Application failed during request deserialization: Can't use an undefined value as an ARRAY reference at /usr/share/perl5/SOAP/Lite.pm line 1667, <GEN7> line 605.
</string></value></member><member><name>faultCode</name><value><string>Client</string></value></member></struct></value></fault></methodResponse>

The packets and length counts look right and I can issue other calls like getfriends with clear auth, and it works perfectly.

Any clues would be helpful.

I'm also wondering if there's more documentation on the Event Properties. The documentation available is kind of confusing and inconsistent - it refers to properties which aren't documented.
linkReply

Comments:
(Deleted comment)
[User Picture]From: thewerewolf
2005-01-04 07:14 pm (UTC)
I've looked through all the .NET libraries for both XMLRPC and for LJ and to be honest, they're all overwhelmingly complex and difficult to use.

My library is already very easy to use and hides most of the complex stuff away.

Mind you, some of this might be documentation issues - we'll see how easy mine is once someone other than myself tries to use it. :)

In this case, the XML generated was very rigid and predictable, so generating my own was trivial. The actual XML-RPC protocol is trivial, and WebClient handles the transport very easily.

This is the same reason I avoided using .NET's XML building libraries - toooo complicated for such a simple task. :)

But I am using their XML parser. I really don't want to write my own version of that.
(Reply) (Parent) (Thread)