<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Kohana simple REST server</title>
	<atom:link href="http://www.ninjapenguin.co.uk/blog/2009/04/05/kohana-simple-rest-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ninjapenguin.co.uk/blog/2009/04/05/kohana-simple-rest-server/</link>
	<description>Personal blog of Matthew Wells</description>
	<lastBuildDate>Tue, 30 Aug 2011 20:59:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Thim</title>
		<link>http://www.ninjapenguin.co.uk/blog/2009/04/05/kohana-simple-rest-server/comment-page-1/#comment-12130</link>
		<dc:creator>Thim</dc:creator>
		<pubDate>Mon, 01 Nov 2010 20:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.ninjapenguin.co.uk/blog/?p=113#comment-12130</guid>
		<description>Hi Matt,
Your proposed SOA and clear example allowed me to kick start my webservice and api, thank you for sharing this. I m going to add the JSON format output because of better JavaScript integration. If you have a GIT hub to share your module that would be even better startpoint for creating a kohana webservice. You can get a free Git or Svn hub/repo at Beanstalk, you could use to put your module on. 

Looking forward for your caching example. 
Keep these examples comming,
Thim</description>
		<content:encoded><![CDATA[<p>Hi Matt,<br />
Your proposed SOA and clear example allowed me to kick start my webservice and api, thank you for sharing this. I m going to add the JSON format output because of better JavaScript integration. If you have a GIT hub to share your module that would be even better startpoint for creating a kohana webservice. You can get a free Git or Svn hub/repo at Beanstalk, you could use to put your module on. </p>
<p>Looking forward for your caching example.<br />
Keep these examples comming,<br />
Thim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.ninjapenguin.co.uk/blog/2009/04/05/kohana-simple-rest-server/comment-page-1/#comment-5553</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sat, 11 Apr 2009 20:15:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.ninjapenguin.co.uk/blog/?p=113#comment-5553</guid>
		<description>Thanks for the comments, my personal preference would always be to use singular entity names, so category as opposed to categories, again this should just be something upon which you standardize (see the inflector::plural() ) helper method!

@Antoine, as I&#039;m sure your aware REST is stateless, so where required authentication details could be passed with each individual request, this could be handled via HTTP BASIC or by accepting username/password as part of the post body. This would be another good shorter topic for another post possibly!

Thanks very much

/Matt</description>
		<content:encoded><![CDATA[<p>Thanks for the comments, my personal preference would always be to use singular entity names, so category as opposed to categories, again this should just be something upon which you standardize (see the inflector::plural() ) helper method!</p>
<p>@Antoine, as I&#8217;m sure your aware REST is stateless, so where required authentication details could be passed with each individual request, this could be handled via HTTP BASIC or by accepting username/password as part of the post body. This would be another good shorter topic for another post possibly!</p>
<p>Thanks very much</p>
<p>/Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antoine Leclair</title>
		<link>http://www.ninjapenguin.co.uk/blog/2009/04/05/kohana-simple-rest-server/comment-page-1/#comment-5550</link>
		<dc:creator>Antoine Leclair</dc:creator>
		<pubDate>Sat, 11 Apr 2009 14:40:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.ninjapenguin.co.uk/blog/?p=113#comment-5550</guid>
		<description>Great article!

It would be nice to share your module.

I was planning to explore the possibility of implementing a RESTful design with Kohana, but you seem to have done a good job already!

How do you manage authentication?</description>
		<content:encoded><![CDATA[<p>Great article!</p>
<p>It would be nice to share your module.</p>
<p>I was planning to explore the possibility of implementing a RESTful design with Kohana, but you seem to have done a good job already!</p>
<p>How do you manage authentication?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: biakaveron</title>
		<link>http://www.ninjapenguin.co.uk/blog/2009/04/05/kohana-simple-rest-server/comment-page-1/#comment-5549</link>
		<dc:creator>biakaveron</dc:creator>
		<pubDate>Sat, 11 Apr 2009 14:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.ninjapenguin.co.uk/blog/?p=113#comment-5549</guid>
		<description>Thanks for great idea, Matt!

I think it is not good idea to create ORM-object at __call() method because of possible different logic...

Additional, what do you think about using GET /service/categories/ instead of GET /service/category/ when we want to get list of objects?</description>
		<content:encoded><![CDATA[<p>Thanks for great idea, Matt!</p>
<p>I think it is not good idea to create ORM-object at __call() method because of possible different logic&#8230;</p>
<p>Additional, what do you think about using GET /service/categories/ instead of GET /service/category/ when we want to get list of objects?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

