<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #webservices</title>
    <link>/tags/webservices/</link>
    <description>Recent bookmarks tagged #webservices</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:46 +0000</lastBuildDate>
    <item>
      <title>Meet Runscope — Runscope Blog</title>
      <link>http://blog.runscope.com/posts/meet-runscope</link>
      <description>Tools that give application developers visibility into the conversations their apps are having with the services they rely on. Tools that make debugging and testing your API integrations as simple as any other line of code.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #dev #gluecon #imported:pinboard #integration #testing #webservices&lt;/p&gt;</description>
      <pubDate>Wed, 22 May 2013 23:39:10 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23669</guid>
      <category>apis</category>
      <category>dev</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>integration</category>
      <category>testing</category>
      <category>webservices</category>
    </item>
    <item>
      <title>REST Litmus Test for Web Frameworks - Stefan Tilkov&#39;s Random Stuff</title>
      <link>http://www.innoq.com/blog/st/2010/07/rest_litmus_test_for_web_frame.html</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #rest #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Mon, 18 Oct 2010 15:45:49 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:14463</guid>
      <category>rest</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
    <item>
      <title>jespern / django-piston / wiki / Home — bitbucket.org</title>
      <link>http://bitbucket.org/jespern/django-piston/wiki/Home</link>
      <description>&#34;A mini-framework for Django for creating RESTful APIs.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #api #django #python #rest #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Mon, 19 Jul 2010 13:59:55 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:13783</guid>
      <category>api</category>
      <category>django</category>
      <category>python</category>
      <category>rest</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
    <item>
      <title>HookPress: Webhooks for WordPress</title>
      <link>http://mitcho.com/blog/projects/hookpress-webhooks-for-wordpress</link>
      <description>&#34;I recently have spent a little time putting together a new WordPress plugin called HookPress. HookPress lets you add webhooks to WordPress, letting you easily develop push notifications or extend WordPress in languages other than PHP.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #hookpress #php #system:host=mitcho.com #webhooks #webservices #wordpress&lt;/p&gt;</description>
      <pubDate>Fri, 07 Aug 2009 16:36:17 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:12486</guid>
      <category>hookpress</category>
      <category>php</category>
      <category>system:host=mitcho.com</category>
      <category>webhooks</category>
      <category>webservices</category>
      <category>wordpress</category>
    </item>
    <item>
      <title>I finally get REST. Wow. - The Tripping Point - Pluralsight Blogs</title>
      <link>http://www.pluralsight.com/community/blogs/tewald/archive/2007/04/26/46984.aspx</link>
      <description>&#34;The essence of REST is to make the states of the protocol explicit and addressible by URIs. The current state of the protocol state machine is represented by the URI you just operated on and the state representation you retrieved. You change state by operating on the URI of the state you&#39;re moving to, making that your new state. A state&#39;s representation includes the links (arcs in the graph) to the other states that you can move to from the current state. This is exactly how browser based apps work, and there is no reason that your app&#39;s protocol can&#39;t work that way too.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #rest #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Mon, 23 Feb 2009 15:00:58 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:12032</guid>
      <category>rest</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
    <item>
      <title>Web Hooks and the Programmable World of Tomorrow - SlideShare</title>
      <link>http://www.slideshare.net/progrium/web-hooks-and-the-programmable-world-of-tomorrow-presentation</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #integration #rest #webdev #webhooks #webservices&lt;/p&gt;</description>
      <pubDate>Mon, 26 Jan 2009 04:16:08 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11936</guid>
      <category>integration</category>
      <category>rest</category>
      <category>webdev</category>
      <category>webhooks</category>
      <category>webservices</category>
    </item>
    <item>
      <title>The Wonderful World of Web Hooks // Notebook // Kyle Slattery</title>
      <link>http://kyleslattery.com/notebook/entries/the-wonderful-world-of-web-hooks</link>
      <description>&#34;The aspect that excites me the most is how easy it is to write a web hook. All you need to have is a cheap PHP host and some basic knowledge about handling POST data, and you&#39;re ready to go. By shortening the learning curve, web hooks make it possible for more people to build on top of existing platforms, leading to a more connected and interesting internet.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #webdev #webhooks #webservices&lt;/p&gt;</description>
      <pubDate>Mon, 26 Jan 2009 04:01:41 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11935</guid>
      <category>webdev</category>
      <category>webhooks</category>
      <category>webservices</category>
    </item>
    <item>
      <title>XML-RPC in Mozilla</title>
      <link>http://www.mozilla.org/projects/xmlrpc</link>
      <description>&#34;Mozilla implements XML-RPC as a JavaScript component.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #firefox #mozilla #webdev #webservices #xmlrpc&lt;/p&gt;</description>
      <pubDate>Wed, 03 Dec 2008 15:34:40 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11732</guid>
      <category>firefox</category>
      <category>mozilla</category>
      <category>webdev</category>
      <category>webservices</category>
      <category>xmlrpc</category>
    </item>
    <item>
      <title>Dare Obasanjo aka Carnage4Life - REST API Design: Invent Media Types, Not Protocols and Understand the Importance of Hyperlinks</title>
      <link>http://www.25hoursaday.com/weblog/2008/10/24/RESTAPIDesignInventMediaTypesNotProtocolsAndUnderstandTheImportanceOfHyperlinks.aspx</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #architecture #atom #atompub #hyperlinks #hypermedia #hypertext #links #opensocial #rest #rss #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Mon, 27 Oct 2008 19:07:20 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11594</guid>
      <category>architecture</category>
      <category>atom</category>
      <category>atompub</category>
      <category>hyperlinks</category>
      <category>hypermedia</category>
      <category>hypertext</category>
      <category>links</category>
      <category>opensocial</category>
      <category>rest</category>
      <category>rss</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
    <item>
      <title>REST APIs must be hypertext-driven » Untangled</title>
      <link>http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven</link>
      <description>&#34;What needs to be done to make the REST architectural style clear on the notion that hypertext is a constraint? In other words, if the engine of application state (and hence the API) is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API. Period. Is there some broken manual somewhere that needs to be fixed?&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #http #hypertext #rant #rest #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Wed, 22 Oct 2008 22:36:35 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11586</guid>
      <category>apis</category>
      <category>http</category>
      <category>hypertext</category>
      <category>rant</category>
      <category>rest</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
    <item>
      <title>Peter Williams - Versioning REST Web Services</title>
      <link>http://barelyenough.org/blog/2008/05/versioning-rest-web-services</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #http #rest #versioning #webservices&lt;/p&gt;</description>
      <pubDate>Wed, 15 Oct 2008 19:49:57 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11542</guid>
      <category>http</category>
      <category>rest</category>
      <category>versioning</category>
      <category>webservices</category>
    </item>
    <item>
      <title>ongoing · Learning REST</title>
      <link>http://www.tbray.org/ongoing/When/200x/2008/10/01/Learning-REST</link>
      <description>&#34;I was talking to a colleague who has to become savvy in a hurry about modern Web applications and he asked “How do I learn about REST?” Good question. I thought of a couple of suggestions, then asked Twitter and got some more. Here they are.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #http #rest #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Thu, 02 Oct 2008 15:29:26 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11477</guid>
      <category>http</category>
      <category>rest</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
    <item>
      <title>Request Weblog #Frog: REST Request</title>
      <link>http://www.crummy.com/2008/08/18/0</link>
      <description>&#34;But on a technical level, the point is not that &#34;whatever!&#34; is evil. The point is that if you chip a piece off &#34;whatever!&#34; and make it mean something specific, you can optimize around the constraints and reap the benefits.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #http #rest #soap #web #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Tue, 19 Aug 2008 14:29:17 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11240</guid>
      <category>http</category>
      <category>rest</category>
      <category>soap</category>
      <category>web</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
    <item>
      <title>Dare Obasanjo aka Carnage4Life - Explaining REST to Damien Katz</title>
      <link>http://www.25hoursaday.com/weblog/2008/08/17/ExplainingRESTToDamienKatz.aspx</link>
      <description>&#34;At this point, the benefits of building RESTful services for the Web should be self evident. The Web has a particular architecture and it makes sense that if you are deploying a service or API on the Web then it should take advantage of this architecture instead of fighting against it. There are millions of deployed clients, servers and intermediaries that support REST and it makes sense to be compatible with their expectations. &#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #rest #soap #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Mon, 18 Aug 2008 00:01:49 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11228</guid>
      <category>apis</category>
      <category>rest</category>
      <category>soap</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
    <item>
      <title>Amazon Web Services Developer Connection : Browser Uploads to S3 using HTML POST Forms</title>
      <link>http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1434</link>
      <description>&#34;Create HTML POST forms that allow your web site visitors to upload files into your S3 account using a standard web browser.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #amazon #s3 #webdev #webservices&lt;/p&gt;</description>
      <pubDate>Fri, 27 Jun 2008 03:06:25 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:10998</guid>
      <category>amazon</category>
      <category>s3</category>
      <category>webdev</category>
      <category>webservices</category>
    </item>
  </channel>
</rss>
