[ale] Implementing XML-RPC

[Denny Chambers]

The client and server both send XML data to each other. The client does 
a POST request. The content should be set to "text/xml". But you really 
don't need to know all of this info, the XML-RPC takes care of the 
transport of information. What you do need is a XML-RPC client that can 
handle Cookies, and 401 authenications request. I am not sure what 
language you are coding this in, but the XML-RPC java code from jakarta 
has a SecureXmlRpcClient that I believe will handle all of your needs. 
You can check out http://ws.apache.org/xmlrpc/. Look at the javadocs for 
this. I have done a little XML-RPC using the XML-RPC-c 
(http://xmlrpc-c.sourceforge.net/), but I am not sure they support 
Cookies or authenications. I don't remember seeing any examples of those.


Denny

Christopher Fowler wrote:

>I'm starting a project to implement XML-RPC on our embedded device. 
>I've looked at the XML-RPC HOWTO and it seem to have left out some
>details.  I need to know how the actual XML-RPC communications is done
>between the client and the server over HTTP.
>
>Questions:
>
>1.  Does the client post a form where data in that form is the actual
>XML-RPC code?  
>
>2.  What does the server send back?  Pure XML or HTML.  
>
>I've looked at the various API's and they do not seem to address
>authentication.  Our device requires a user to loing via a form at
>http://ip/login.  After the client receives a cookie they can then easiy
>get to http://ip/xml-rpc and the start sending and receiving data.  
>
>
>Thanks,
>Chris
>
>_______________________________________________
>Ale mailing list
>Ale at ale.org
>http://www.ale.org/mailman/listinfo/ale
>
>
>  
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3190 bytes
Desc: S/MIME Cryptographic Signature