<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Getting on the REST bandwagon</title>
	<atom:link href="http://blog.erace.pl/2009/01/17/getting-on-the-rest-bandwagon/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.erace.pl/2009/01/17/getting-on-the-rest-bandwagon/</link>
	<description>The history of the Polish software company.</description>
	<lastBuildDate>Tue, 11 Oct 2011 19:45:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: erace</title>
		<link>http://blog.erace.pl/2009/01/17/getting-on-the-rest-bandwagon/#comment-11</link>
		<dc:creator><![CDATA[erace]]></dc:creator>
		<pubDate>Mon, 19 Jan 2009 11:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.erace.pl/?p=25#comment-11</guid>
		<description><![CDATA[I would like to create an application with GWT therefore I believe there is no need for a search form. 

I was thinking to construct the search query like this:

http://unisalveo.org/foods?par1=x&amp;par2=2 

which I guess is in line with your first suggestion. I will have to look into the reasoning behind 2nd type of URL (GData). Thx for the hint!]]></description>
		<content:encoded><![CDATA[<p>I would like to create an application with GWT therefore I believe there is no need for a search form. </p>
<p>I was thinking to construct the search query like this:</p>
<p><a href="http://unisalveo.org/foods?par1=x&#038;par2=2" rel="nofollow">http://unisalveo.org/foods?par1=x&#038;par2=2</a> </p>
<p>which I guess is in line with your first suggestion. I will have to look into the reasoning behind 2nd type of URL (GData). Thx for the hint!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Moore</title>
		<link>http://blog.erace.pl/2009/01/17/getting-on-the-rest-bandwagon/#comment-10</link>
		<dc:creator><![CDATA[Jon Moore]]></dc:creator>
		<pubDate>Sun, 18 Jan 2009 15:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.erace.pl/?p=25#comment-10</guid>
		<description><![CDATA[Just a comment on your URI construction around searching. It&#039;s probably easier to think in terms of two resources:

http://unisalveo.org/foods/search_form

which you can GET for an HTML page containing a search form. Then have the form on that page use method=&quot;get&quot; and send the action to:

http://unisalveo.org/foods?q=search_term_goes_here

or, in a style similar to Google&#039;s GData API, maybe the URL looks like:

http://unisalveo.org/foods/-/query/search_term_goes_here]]></description>
		<content:encoded><![CDATA[<p>Just a comment on your URI construction around searching. It&#8217;s probably easier to think in terms of two resources:</p>
<p><a href="http://unisalveo.org/foods/search_form" rel="nofollow">http://unisalveo.org/foods/search_form</a></p>
<p>which you can GET for an HTML page containing a search form. Then have the form on that page use method=&#8221;get&#8221; and send the action to:</p>
<p><a href="http://unisalveo.org/foods?q=search_term_goes_here" rel="nofollow">http://unisalveo.org/foods?q=search_term_goes_here</a></p>
<p>or, in a style similar to Google&#8217;s GData API, maybe the URL looks like:</p>
<p><a href="http://unisalveo.org/foods/-/query/search_term_goes_here" rel="nofollow">http://unisalveo.org/foods/-/query/search_term_goes_here</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

