<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Nhoizey's Favorite Links on rest from Diigo</title>
    <link>http://www.diigo.com/user/Nhoizey/rest</link>
    <pubDate>Fri, 06 Jun 2008 13:35:55 -0000</pubDate>
    <lastBuildDate>Fri, 06 Jun 2008 13:35:55 -0000</lastBuildDate>
    <item>
      <title>Describe REST Web services with WSDL 2.0</title>
      <link>http://www.ibm.com/developerworks/webservices/library/ws-restwsdl</link>
      <description>&lt;p&gt;A key component of a Web service is a formal description with Web Services Description Language (WSDL). Until recently there was no formal language to describe REpresentational State Transfer (REST) Web services—now there's WSDL 2.0.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/WSDL' rel='tag'&gt;WSDL&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/REST' rel='tag'&gt;REST&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/Web+Services' rel='tag'&gt;Web Services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/WSDL+2.0' rel='tag'&gt;WSDL 2.0&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/clevermarks' rel='tag'&gt;clevermarks&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Fri, 06 Jun 2008 13:35:55 -0000</pubDate>
    </item>
    <item>
      <title>InfoQ: Hypermedia in RESTful applications</title>
      <link>http://www.infoq.com/articles/mark-baker-hypermedia</link>
      <description>&lt;p&gt;Flickr's current approach of requiring that clients possess Flickr-specific knowledge in order to progress from one application state to another, is simply another way of saying that they have a proprietary application model. Not only is it proprietary th&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/flickr' rel='tag'&gt;flickr&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/hypermedia' rel='tag'&gt;hypermedia&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/API' rel='tag'&gt;API&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/REST' rel='tag'&gt;REST&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/architecture' rel='tag'&gt;architecture&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 05 Mar 2008 15:46:18 -0000</pubDate>
    </item>
    <item>
      <title>REST vs. SOAP at Amazon</title>
      <link>http://www.oreillynet.com/pub/wlg/3005</link>
      <description>&lt;p&gt;Amazon has both SOAP and REST interfaces to their web services, and 85% of their usage is of the REST interface. Despite all of the corporate hype over the SOAP stack, this is pretty compelling evidence that developers like the simpler REST approach.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/REST' rel='tag'&gt;REST&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/SOAP' rel='tag'&gt;SOAP&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/Amazon' rel='tag'&gt;Amazon&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/API' rel='tag'&gt;API&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/Web_Services' rel='tag'&gt;Web_Services&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 05 Mar 2008 11:04:59 -0000</pubDate>
    </item>
    <item>
      <title>O'Reilly Network -- Stewart Butterfield on Flickr</title>
      <link>http://www.oreillynet.com/pub/a/network/2005/02/04/sb_flckr.html</link>
      <description>&lt;p&gt;I think we had one person inquire about using the SOAP version of the API. I don't know if any apps were actually built. There is at least one application built on XML-RPC. But all the others--I don't even know how many there are--are built on the REST AP&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/Flickr' rel='tag'&gt;Flickr&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/API' rel='tag'&gt;API&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/XML-RPC' rel='tag'&gt;XML-RPC&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/REST' rel='tag'&gt;REST&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/SOAP' rel='tag'&gt;SOAP&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 05 Mar 2008 11:04:09 -0000</pubDate>
    </item>
    <item>
      <title>WSO2 Web Services Framework for PHP | WSO2 Oxygen Tank</title>
      <link>http://wso2.org/projects/wsf/php</link>
      <description>&lt;p&gt;WSO2 WSF/PHP is a complete solution for building and deploying Web services, and is the only PHP extension with the widest range of WS-* specification implementations&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/php' rel='tag'&gt;php&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/Web_Services' rel='tag'&gt;Web_Services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/dev' rel='tag'&gt;dev&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/WS-%2A' rel='tag'&gt;WS-*&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/wsdl' rel='tag'&gt;wsdl&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Tue, 12 Feb 2008 12:01:50 -0000</pubDate>
    </item>
    <item>
      <title>L'architecture orientée ressource pour faire des services web RESTful - Biologeek : Ubuntu, bio-informatique et geekeries libres d'un bio-informaticien au quotidien.</title>
      <link>http://www.biologeek.com/journal/index.php/architecture-orientee-ressource-pour-faire-des-services-web-restful</link>
      <description>&lt;p&gt;Le plus gros défaut de REST, c'est sûrement de se limiter à la comparaison des 4 verbes HTTP (GET, POST, PUT et DELETE) aux 4 actions possibles sur des données issues de bases de données (Retrieve, Create, Update et Delete soit CRUD)&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/crud' rel='tag'&gt;crud&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/architecture' rel='tag'&gt;architecture&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/ressource' rel='tag'&gt;ressource&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/dev' rel='tag'&gt;dev&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 28 Nov 2007 07:34:31 -0000</pubDate>
    </item>
    <item>
      <title>Pete Lacey’s Weblog :: What is SOA?</title>
      <link>http://wanderingbarque.com/nonintersecting/2007/10/05/what-is-soa</link>
      <description>&lt;p&gt;Once again the participants in the SOA discussion group have got themselves all riled up about what exactly SOA is and why it may or may not be working.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soa' rel='tag'&gt;soa&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/architecture' rel='tag'&gt;architecture&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soap' rel='tag'&gt;soap&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Mon, 08 Oct 2007 11:09:13 -0000</pubDate>
    </item>
    <item>
      <title>REST vs. WS-*: War is Over (If You Want It) :: David Chappell :: Blog</title>
      <link>http://www.davidchappell.com/blog/2007/06/rest-vs-ws-war-is-over-if-you-want-it.html</link>
      <description>&lt;p&gt;REST is for data-oriented applications that focus on create/read/update/delete scenarios. Solution based on WS-* for service/method-oriented applications, especially those that need more advanced behaviors such as transactions and more-than-basic security&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/REST' rel='tag'&gt;REST&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/architecture' rel='tag'&gt;architecture&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soap' rel='tag'&gt;soap&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soa' rel='tag'&gt;soa&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Mon, 09 Jul 2007 07:30:41 -0000</pubDate>
    </item>
    <item>
      <title>RestWiki: Front Page</title>
      <link>http://rest.blueoxen.net/cgi-bin/wiki.pl?FrontPage</link>
      <description>&lt;p&gt;Le Wiki de REST&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/xml' rel='tag'&gt;xml&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/http' rel='tag'&gt;http&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soap' rel='tag'&gt;soap&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:55:50 -0000</pubDate>
    </item>
    <item>
      <title>Ce qui manque encore à l'informatique Internet - La chronique d'Alain Lefebvre</title>
      <link>http://solutions.journaldunet.com/0502/050208_chro_lefevbre.shtml</link>
      <description>&lt;p&gt;Un peu de tout dans cette nouvelle chronique de Alain Lefebvre&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/client_riche' rel='tag'&gt;client_riche&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/semweb' rel='tag'&gt;semweb&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:52:58 -0000</pubDate>
    </item>
    <item>
      <title>What if SOAP had never happened?</title>
      <link>http://www.onlamp.com/pub/wlg/6563</link>
      <description>&lt;p&gt;SOAP and its ever-growing family of specifications emerged because vendors needed something more concrete than design services to sell their customers, and because the hype wave around XML had promised too much that couldn't be delivered immediately.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soap' rel='tag'&gt;soap&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:51:18 -0000</pubDate>
    </item>
    <item>
      <title>RESTGate Browser for REST-style Web Services</title>
      <link>http://www.osmoticweb.com/restgate</link>
      <description>&lt;p&gt;RESTGate is a Web-based client for REST-style Web Services. Any Web browser can be used to send arbitrary HTTP GET requests by manipulating the URL. It used to be necessary to write an HTML form or a small program to send POST, PUT and DELETE messages....&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/client' rel='tag'&gt;client&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:50:35 -0000</pubDate>
    </item>
    <item>
      <title>Adactio: Journal - Introducing Adactio Elsewhere</title>
      <link>http://adactio.com/journal/display.php/20050428161517.xml</link>
      <description>&lt;p&gt;Toutes les hypes mises en oeuvre en un seul endroit : Ajax, REST et les API de Flickr, Amazon, Del.icio.us et Upcoming&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/buzz' rel='tag'&gt;buzz&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/del.icio.us' rel='tag'&gt;del.icio.us&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/flickr' rel='tag'&gt;flickr&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/api' rel='tag'&gt;api&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:47:42 -0000</pubDate>
    </item>
    <item>
      <title>Connecting Social Content Services using FOAF, RDF and REST</title>
      <link>http://idealliance.org/proceedings/xtech05/papers/02-07-04/</link>
      <description>&lt;p&gt;A growing number of &amp;quot;social content&amp;quot; applications such as Flickr, del.icio.us, audioscrobbler, and AllConsuming are making open web services part of their core offering to end users. These interfaces allow users to query, share, and manipulate the data...&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/social' rel='tag'&gt;social&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/del.icio.us' rel='tag'&gt;del.icio.us&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/flickr' rel='tag'&gt;flickr&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:46:57 -0000</pubDate>
    </item>
    <item>
      <title>Apprendre REST - un style d'architecture du Web</title>
      <link>http://www.la-grange.net/2005/05/rest/index.html</link>
      <description>&lt;p&gt;Traduction française des articles de Joe Gregorio sur REST&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soap' rel='tag'&gt;soap&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/lang_fr' rel='tag'&gt;lang_fr&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/clevermarks' rel='tag'&gt;clevermarks&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:44:23 -0000</pubDate>
    </item>
    <item>
      <title>Pragmatics</title>
      <link>http://pluralsight.com/blogs/dbox/archive/2006/02/17/18869.aspx</link>
      <description>&lt;p&gt;how to handle an internal product debate around REST vs. SOAP&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soap' rel='tag'&gt;soap&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/d%C3%A9bat' rel='tag'&gt;débat&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/vs' rel='tag'&gt;vs&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:38:17 -0000</pubDate>
    </item>
    <item>
      <title>REST wins, no-one goes home [@lesscode.org]</title>
      <link>http://lesscode.org/2006/03/19/rest-wins-no-one-goes-home</link>
      <description>&lt;p&gt;Let’s be realistic. No software architecture can truly withstand implementation. REST is really great, but on the web, there is plenty of detail work to be cleared out, like push, containership, encoding, side-effected GETs, curse-of-popularity, queu...&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web' rel='tag'&gt;web&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soap' rel='tag'&gt;soap&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/architecture' rel='tag'&gt;architecture&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:38:16 -0000</pubDate>
    </item>
    <item>
      <title>Going Down To The Crossroads…</title>
      <link>http://pluralsight.com/blogs/dbox/archive/2006/03/18/20235.aspx</link>
      <description>&lt;p&gt;catalog what resources MS has already committed to the XML/HTTP/REST technologies&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/microsoft' rel='tag'&gt;microsoft&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/support' rel='tag'&gt;support&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:38:16 -0000</pubDate>
    </item>
    <item>
      <title>eXist : Une base de données XML interrogeable avec XPath et XQuery</title>
      <link>http://xmlfr.org/actualites/tech/040210-0001</link>
      <description>&lt;p&gt;eXist peut non seulement s'intégrer très facilement dans une application Java (via une servlet - XQueryServlet -, un composant Cocoon - XQueryGenerator - , ou l'utilisation de l'API XML:DB), mais elle peut également être utilisée dans de nombreux ...&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/xml' rel='tag'&gt;xml&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/xquery' rel='tag'&gt;xquery&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/python' rel='tag'&gt;python&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/php' rel='tag'&gt;php&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:37:48 -0000</pubDate>
    </item>
    <item>
      <title>The Cafes » REST vs. WS-*: A Parable</title>
      <link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/</link>
      <description>&lt;p&gt;A couple of years ago Water Supply-Strategic Tactical Air Recycling (WS-STAR) opened up a branch in our town. WS-* (as my IM crazy kids would type) came about from the merger of Secure Operations Air and Power (SOAP) with Expert Machine Lubrication: Ra...&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey/rest' rel='tag'&gt;rest&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/web_services' rel='tag'&gt;web_services&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/soap' rel='tag'&gt;soap&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/xml-rpc' rel='tag'&gt;xml-rpc&lt;/a&gt; &lt;a href='http://www.diigo.com/user/nhoizey/vs' rel='tag'&gt;vs&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href='http://www.diigo.com/user/nhoizey'&gt;nhoizey&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Apr 2007 06:37:21 -0000</pubDate>
    </item>
    <ttl>60</ttl>
  </channel>
</rss>