Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

XML-RPC or SOAP-RPC !!!!!!!  RSS feed

 
Jacob George
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I have over 2 years of programming experiance in java, but am new to the web-service stuff. Please help me in getting started. I recently heard one audiocast from java.sun.com on SOAP-RPC and I throught that its a standard defined for messaging and making RPC. But when I searched the web, I found XML-RPC also. So, whats the difference between these two. On encountering a situation, when should I choose SOAP-RPC over XML-RPC? Or is SOAP-RPC a much more matured model built over XML-RPC? Any help would be appreciated.
Thanking You..
regards Jacob
 
Petr Sturc
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jacob,
I am not expert in SOAP, but XML-RPC I use lot in our projects. As far as I know the general principle of both technologies is the same. The XML-RPC is much lighter. It defines only small set of types - string, int, double, date, boolean, base64 and two aggregate types struct and array. In contrast to SOAP, there is no way to define custome types. Also order of arguments is significant in XML-RPC.
XML-RPC is something you can work with after 5 minutes reading of Spec. You don't have to cope with namespaces, envelopes etc. BTW, there is also XML-RPC implementation for JavaPhones - it's about 20kB including XML parser. If your have memory of performance constraints XML-RPC is probably your choice.
Best regards,
Petr
 
Jacob George
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Petr Sturc:
Jacob,
I am not expert in SOAP, but XML-RPC I use lot in our projects. As far as I know the general principle of both technologies is the same. The XML-RPC is much lighter. It defines only small set of types - string, int, double, date, boolean, base64 and two aggregate types struct and array. In contrast to SOAP, there is no way to define custome types. Also order of arguments is significant in XML-RPC.
XML-RPC is something you can work with after 5 minutes reading of Spec. You don't have to cope with namespaces, envelopes etc. BTW, there is also XML-RPC implementation for JavaPhones - it's about 20kB including XML parser. If your have memory of performance constraints XML-RPC is probably your choice.
Best regards,
Petr

Thanks pal.
warmth Jacob
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!