<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ryan norris &#187; soa</title>
	<atom:link href="http://www.ryannorris.com/tag/soa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ryannorris.com</link>
	<description>managing software teams and delivering great results</description>
	<lastBuildDate>Fri, 25 Jun 2010 13:44:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Simplifying XML-based RESTful services in Elgg</title>
		<link>http://www.ryannorris.com/2009/02/03/simplifying-xml-based-restful-services-in-elgg/</link>
		<comments>http://www.ryannorris.com/2009/02/03/simplifying-xml-based-restful-services-in-elgg/#comments</comments>
		<pubDate>Tue, 03 Feb 2009 17:50:09 +0000</pubDate>
		<dc:creator>Ryan Norris</dc:creator>
				<category><![CDATA[Building Better Software]]></category>
		<category><![CDATA[elgg]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[soa]]></category>

		<guid isPermaLink="false">http://blog.ryannorris.com/?p=3</guid>
		<description><![CDATA[Playing around with elgg, it's a typical PHP project where the documentation grows from understanding it's quirks.]]></description>
			<content:encoded><![CDATA[<p><a title="Elgg - Social Networking" href="http://www.elgg.org">elgg</a> is a PHP-based social networking wonder that we&#8217;ve been using at Medullan for some internal stuff lately.  One of my interests was to see what type of tooling could be built around it &#8211; desktop widgets, firefox extensions, etc.  It appeared they had a RESTful API of sorts, but the service results were always rendered through the standard HTML view.  Everything I found seemed to say I was stuck with this.  Not so.</p>
<p>If you attach a querystring parameter to your request called view, elgg will output your RESTful service result to any of the supported formats &#8211; HTML, XML, JSON, FOAF, etc.</p>
<p>So if I have a method called &#8220;print&#8221; <a title="How to expose restful services in elgg" href="http://community.elgg.org/pg/pages/view/70/">exposed as documented by elgg</a>, I can have the result returned to me as XML very easily:</p>
<p>http://localhost:8080/elgg/pg/api/rest?method=print&amp;view=xml</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ryannorris.com/2009/02/03/simplifying-xml-based-restful-services-in-elgg/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
