On Dec 7, 2007 5:09 PM, Colin Burnett <<a href="mailto:cmlburnett@gmail.com">cmlburnett@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If I have to use SOAP or XML-RPC, I pick XML-RPC. IMHO, SOAP is<br>bloated and overly complex so I stay away. NuSOAP for PHP vs. SOAPpy<br>for python is like night and day, respectively. Though python has a<br>significant advantage (in terms of coding simplicity) by having
<br>first-class functions. Setting up a client or server with SOAPpy is<br>like 2 lines.<br></blockquote></div><br>Actually, this is very much my configuration. My application is using NuSOAP and I'm having problems with it in PHP5. Unfortunately, the pickle approach won't work for me (unless there's some magic I'm not aware of) because I use PHP on the server and Python and PHP on the client.
<br><br>However, the concept is something I'm considering. If I made a RESTful service, the client could request the results to be serialized in a way it likes by inclusion of a header tag (Accept-Encoding). So, for example, it could send Accept-Encoding: text/json\r\n and have the results in JSON or text/xml for XML.
<br><br>For me, I'm getting tired of everything running in a browser, so I'm exploring (in my personal time, therefore at a slow pace) creating applications on the desktop that interoperate with web services or web applications. Therefore I want to start thinking about this type of feature for all my web applications.
<br clear="all"><br>-- <br>Matthew Nuzum<br>newz2000 on freenode