<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

  <channel>
    <title>vsbabu.org : services</title>
    <link>http://vsbabu.org/mt/archives/categories/services/</link>
    <description>Gluing passing thoughts to foregone conclusions</description>
    <dc:language>en-us</dc:language>
    <dc:creator>vsbabu@gmail.com</dc:creator>
    <dc:rights>Copyright 2008</dc:rights>
    <dc:date>2003-09-08T10:39:31+05:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=2.661" />
    <admin:errorReportsTo rdf:resource="mailto:vsbabu@gmail.com"/>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

    <item>
      <title>Web services notes</title>
      <link>http://vsbabu.org/mt/archives/2003/09/08/web_services_notes.html</link>
      <description>Trinetre raises some interesting observations about XML-RPC and web services.</description>
      <guid isPermaLink="false">881@http://vsbabu.org/mt/</guid>
      <content:encoded><![CDATA[<p>
Srijith asks: <a href="http://www.srijith.net/trinetre/archives/2003/09/08/index.shtml#000423">Why not a simple POST as a client?</a>, for example, for Weblogs.com ping. I started typing this comment in
his page - it became slightly long that I thought I'll post it here.
</p>

<p>
XML-RPC (and SOAP) try to make a common vocabulary for passing data back and forth. You can define variable name, variable type, value etc. This particular example of pings doesn't really need all that, so it is not that entertaining.
</p>]]></content:encoded>
      <dc:subject>services</dc:subject>
      <dc:date>2003-09-08T10:39:31+05:00</dc:date>
    </item>
    <item>
      <title>Handling attachments in SOAP</title>
      <link>http://vsbabu.org/mt/archives/2002/02/26/handling_attachments_in_soap.html</link>
      <description>developerWorks: &quot;Web services will require the ability to send more than just text messages between services in a process. Often...</description>
      <guid isPermaLink="false">130@http://vsbabu.org/mt/</guid>
      <content:encoded><![CDATA[<p><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-soapatt/?loc=dwmain">developerWorks</a>: <em>"Web services will require the ability to send more than just text messages between services in a process. Often it will involve complex data types such as language structures, multimedia files, and even other embedded messages. This article takes a look at how the SOAP with Attachments  specification can be used to send such information. It provides a programming example of how to handle custom data type mapping and attachments in your SOAP services."</em></p>

<p>Another set of articles from the same site about <a href="http://www-106.ibm.com/developerworks/library/ws-pyth6/">Python SOAP libraries</a>.</p>

<p>I'm now a big fan of <a href="http://www.xmlrpc.com/">XML-RPC</a>, mainly due to its simplicity, availability of implementations and support in Zope. Since some of our code is still in ASP, I need to figure out how to make standards that separate function from presentation - yeah, the holy grail of web programming - using ASP. Then, <a href="http://aspxmlrpc.sourceforge.net/">ASP XML-RPC</a>, we can easily reuse the functionality over the network. Must be tough to do it in VBScript where objects seldom get out of memory even after being used :-(</p>]]></content:encoded>
      <dc:subject>services</dc:subject>
      <dc:date>2002-02-26T19:04:28+05:00</dc:date>
    </item>


  </channel>
</rss>

