<?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: RESTEasy Forums Online</title>
	<atom:link href="http://www.damnhandy.com/2007/03/05/resteasy-forums-online/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.damnhandy.com/2007/03/05/resteasy-forums-online/</link>
	<description>A blog about Java, REST, and other stuff.</description>
	<lastBuildDate>Fri, 09 Jul 2010 15:26:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Chaula Ganatra</title>
		<link>http://www.damnhandy.com/2007/03/05/resteasy-forums-online/comment-page-1/#comment-121616</link>
		<dc:creator>Chaula Ganatra</dc:creator>
		<pubDate>Fri, 27 Nov 2009 10:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/03/05/resteasy-forums-online/#comment-121616</guid>
		<description>We are having our web application, which accepts data (different ids) in hashed values.Now we are planning to expose some part of our web app as REST based API and we are planning to go with RESTEasy. 
Now the query is : should we only return hashed values in xml to client?
Currently we are having this approach only when we return data to our xsl. So in any next client request, hashed ids will be passed in request parameter. Should the REST based API return any plain ids in XML,to the client? Please let me know your views on this.</description>
		<content:encoded><![CDATA[<p>We are having our web application, which accepts data (different ids) in hashed values.Now we are planning to expose some part of our web app as REST based API and we are planning to go with RESTEasy.<br />
Now the query is : should we only return hashed values in xml to client?<br />
Currently we are having this approach only when we return data to our xsl. So in any next client request, hashed ids will be passed in request parameter. Should the REST based API return any plain ids in XML,to the client? Please let me know your views on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chaula Ganatra</title>
		<link>http://www.damnhandy.com/2007/03/05/resteasy-forums-online/comment-page-1/#comment-130320</link>
		<dc:creator>Chaula Ganatra</dc:creator>
		<pubDate>Fri, 27 Nov 2009 10:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/03/05/resteasy-forums-online/#comment-130320</guid>
		<description>We are having our web application, which accepts data (different ids) in hashed values.Now we are planning to expose some part of our web app as REST based API and we are planning to go with RESTEasy. 
Now the query is : should we only return hashed values in xml to client?
Currently we are having this approach only when we return data to our xsl. So in any next client request, hashed ids will be passed in request parameter. Should the REST based API return any plain ids in XML,to the client? Please let me know your views on this.</description>
		<content:encoded><![CDATA[<p>We are having our web application, which accepts data (different ids) in hashed values.Now we are planning to expose some part of our web app as REST based API and we are planning to go with RESTEasy.<br />
Now the query is : should we only return hashed values in xml to client?<br />
Currently we are having this approach only when we return data to our xsl. So in any next client request, hashed ids will be passed in request parameter. Should the REST based API return any plain ids in XML,to the client? Please let me know your views on this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
