<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - RFC: REST-RPC</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Wed, 19 Jun 2013 14:01:16 -0400</pubDate>


    <item>

        <title>What a joke!</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[How thrilling: another amateur RPC specification.  This stuff seems to attract only those who deal exclusively with trivial cases.<br><br>When I saw the encoding that this &quot;new&quot; REST-RPC uses, I almost snorted beer up my nose....]]></description>
        

        <pubDate>Tue, 07 Mar 2006 23:41:30 -0500</pubDate>

        

        <jf:creationDate>Tue, 07 Mar 2006 23:41:30 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 07 Mar 2006 23:41:30 -0500</jf:modificationDate>
        <jf:date>Mar 7, 2006</jf:date>
        <jf:author>Eron Wright</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Definitional Problem</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[I see the main issue as a definitional one. Is all that is not WS/SOAP REST? No - not really - REST has to have some key unambiguous concepts which do not necessarily coincide with the complement of SOAP. In other words, not all XML/HTTP or POX (Plain...]]></description>
        

        <pubDate>Sat, 04 Mar 2006 00:06:32 -0500</pubDate>

        

        <jf:creationDate>Sat, 04 Mar 2006 00:06:32 -0500</jf:creationDate>
        <jf:modificationDate>Sat, 04 Mar 2006 00:06:32 -0500</jf:modificationDate>
        <jf:date>Mar 4, 2006</jf:date>
        <jf:author>Andre Mesarovic</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>for simple use url form encoding</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[That's all you need to send messages over HTTP. Anything else is just complexification.]]></description>
        

        <pubDate>Thu, 02 Mar 2006 15:54:57 -0500</pubDate>

        

        <jf:creationDate>Thu, 02 Mar 2006 15:54:57 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 02 Mar 2006 15:54:57 -0500</jf:modificationDate>
        <jf:date>Mar 2, 2006</jf:date>
        <jf:author>valraven smith</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>REST-RPC an Oxymoran?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[<blockquote>I was indeed quite confused by this &quot;REST-RPC&quot; title that you gave to this discussion. I'd definitely prefer the &quot;POX-RPC&quot; name which is closer to your original source of inspiration (XML-RPC).</blockquote><br>We will...]]></description>
        

        <pubDate>Wed, 01 Mar 2006 16:25:41 -0500</pubDate>

        

        <jf:creationDate>Wed, 01 Mar 2006 16:25:41 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 01 Mar 2006 16:25:41 -0500</jf:modificationDate>
        <jf:date>Mar 1, 2006</jf:date>
        <jf:author>Ernst de Haan</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>CORBA is easy</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[<blockquote>CORBA, the IBM San Fransisco framework and SOAP fit in the same category. You can do powerful things with them, but it comes with a big cost in terms of complexity and bloat.</blockquote><br>CORBA being difficult is a myth. For simple...]]></description>
        

        <pubDate>Wed, 01 Mar 2006 15:43:26 -0500</pubDate>

        

        <jf:creationDate>Wed, 01 Mar 2006 15:43:26 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 01 Mar 2006 15:43:26 -0500</jf:modificationDate>
        <jf:date>Mar 1, 2006</jf:date>
        <jf:author>Juergen Weber</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>REST != RPC</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[Ernst,<br><br>That was my point precisely.  If people form the impression that REST means &quot;no documents&quot;, REST will be discredited.]]></description>
        

        <pubDate>Wed, 01 Mar 2006 07:45:35 -0500</pubDate>

        

        <jf:creationDate>Wed, 01 Mar 2006 07:45:35 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 01 Mar 2006 07:45:35 -0500</jf:modificationDate>
        <jf:date>Mar 1, 2006</jf:date>
        <jf:author>vantheip</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>REST-RPC an Oxymoran?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[Ernst,<br><br>I was indeed quite confused by this &quot;REST-RPC&quot; title that you gave to this discussion. I'd definitely prefer the &quot;POX-RPC&quot; name which is closer to your original source of inspiration (XML-RPC).<br><br>Also, I don't agree...]]></description>
        

        <pubDate>Wed, 01 Mar 2006 07:25:03 -0500</pubDate>

        

        <jf:creationDate>Wed, 01 Mar 2006 07:25:03 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 01 Mar 2006 07:25:03 -0500</jf:modificationDate>
        <jf:date>Mar 1, 2006</jf:date>
        <jf:author>Jerome Louvel</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>REST-RPC an Oxymoran?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[<blockquote>Is this approach RESTful?  My understanding is that REST is usually <i>contrasted</i> with RPC based approaches.  REST-RPC sounds to my ears like 'procedural object-oriented programming', or military intelligence -- a contradiction in...]]></description>
        

        <pubDate>Wed, 01 Mar 2006 04:31:17 -0500</pubDate>

        

        <jf:creationDate>Wed, 01 Mar 2006 04:31:17 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 01 Mar 2006 04:31:17 -0500</jf:modificationDate>
        <jf:date>Mar 1, 2006</jf:date>
        <jf:author>Kit Davies</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>REST-RPC an Oxymoran?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[Steve,<br><blockquote>Is this approach RESTful? My understanding is that REST is usually <i>contrasted</i> with RPC based approaches.</blockquote><br>No it's not completely RESTful, indeed. While SOAP is document-oriented, REST is resource-oriented and...]]></description>
        

        <pubDate>Wed, 01 Mar 2006 04:25:29 -0500</pubDate>

        

        <jf:creationDate>Wed, 01 Mar 2006 04:25:29 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 01 Mar 2006 04:25:29 -0500</jf:modificationDate>
        <jf:date>Mar 1, 2006</jf:date>
        <jf:author>Ernst de Haan</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>RPC is dead, long live RPC?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[<blockquote> why do you consider a documented-oriented interface a necessity?</blockquote>I don't consider it necessary, I consider it convenient and less maintenance over the long haul.  I'm a big fan of one way to get the data - not one way for this...]]></description>
        

        <pubDate>Tue, 28 Feb 2006 17:33:11 -0500</pubDate>

        

        <jf:creationDate>Tue, 28 Feb 2006 17:33:11 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 28 Feb 2006 17:33:11 -0500</jf:modificationDate>
        <jf:date>Feb 28, 2006</jf:date>
        <jf:author>Adam Spencer</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>RPC is dead, long live RPC?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[<blockquote>I don't know which RPC technology you are referring to, but with REST-RPC, there is virtually no overhead. Here's an example of a request:<blockquote>GET /?_function=GetCart&amp;amp;cart=1563 HTTP/1.1Host: test.rest-rpc.orgAccept:...]]></description>
        

        <pubDate>Tue, 28 Feb 2006 17:28:47 -0500</pubDate>

        

        <jf:creationDate>Tue, 28 Feb 2006 17:28:47 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 28 Feb 2006 17:28:47 -0500</jf:modificationDate>
        <jf:date>Feb 28, 2006</jf:date>
        <jf:author>William Childers</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>REST-RPC an Oxymoran?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[Is this approach RESTful?  My understanding is that REST is usually <i>contrasted</i> with RPC based approaches.  REST-RPC sounds to my ears like 'procedural object-oriented programming', or military intelligence -- a contradiction in terms.<br><br>With...]]></description>
        

        <pubDate>Tue, 28 Feb 2006 17:20:00 -0500</pubDate>

        

        <jf:creationDate>Tue, 28 Feb 2006 17:20:00 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 28 Feb 2006 17:20:00 -0500</jf:modificationDate>
        <jf:date>Feb 28, 2006</jf:date>
        <jf:author>Stephen Molitor</jf:author>
        <jf:replyCount>5</jf:replyCount>
    </item>


    <item>

        <title>RPC is dead, long live RPC?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[<blockquote>How is this different from a regular HTML request with arbitrary character data in response?</blockquote><br>Here the difference is the definition of the tags to be used and their meaning. HTML is aimed at visual markup (for display to...]]></description>
        

        <pubDate>Tue, 28 Feb 2006 16:51:28 -0500</pubDate>

        

        <jf:creationDate>Tue, 28 Feb 2006 16:51:28 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 28 Feb 2006 16:51:28 -0500</jf:modificationDate>
        <jf:date>Feb 28, 2006</jf:date>
        <jf:author>Ernst de Haan</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Whats the point?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[<blockquote>Why would you use an REST-RPC when you could just do a REST call returning bespoke XML?  Need data types? Use XML Schema or custom DTDs.</blockquote><br>Applying plain REST makes sense.<br><br>However, defining an RPC protocol gives...]]></description>
        

        <pubDate>Tue, 28 Feb 2006 16:41:57 -0500</pubDate>

        

        <jf:creationDate>Tue, 28 Feb 2006 16:41:57 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 28 Feb 2006 16:41:57 -0500</jf:modificationDate>
        <jf:date>Feb 28, 2006</jf:date>
        <jf:author>Ernst de Haan</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>RPC is dead, long live RPC?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=39207</link>

        

        
            <description><![CDATA[<blockquote>with REST-RPC, there is virtually no overhead. Here's an example of a request:<blockquote>GET /?_function=GetCart&amp;amp;cart=1563 HTTP/1.1Host: test.rest-rpc.orgAccept: text/xmlConnection: close</blockquote>An example of a...]]></description>
        

        <pubDate>Tue, 28 Feb 2006 15:58:40 -0500</pubDate>

        

        <jf:creationDate>Tue, 28 Feb 2006 15:58:40 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 28 Feb 2006 15:58:40 -0500</jf:modificationDate>
        <jf:date>Feb 28, 2006</jf:date>
        <jf:author>Michael Jouravlev</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>



</channel>
</rss>

