<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>/var/log/mind - Latest Comments in Fomenting unREST : Is RESTfulness a semantics game ? Why does REST require statelessness ?</title><link>http://var-log-mind.disqus.com/</link><description>Dhananjay Nene’s free (as in free speech) opinions on all things related to Software Engineering</description><atom:link href="https://var-log-mind.disqus.com/fomenting_unrest_is_restfulness_a_semantics_game_why_does_rest_require_statelessness/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 09 Jun 2009 16:27:23 -0000</lastBuildDate><item><title>Re: Fomenting unREST : Is RESTfulness a semantics game ? Why does REST require statelessness ?</title><link>http://blog.dhananjaynene.com/2008/11/rest-fomenting-unrest-is-restfulness-a-semantics-game-why-does-rest-require-statelessness/#comment-442489656</link><description>&lt;p&gt;Of course there is state in the server - it would be a very boring application otherwise!  Its the communication that needs to be stateless, a principle that's violated by the use of cookies (and by some uses of headers also).&lt;/p&gt;&lt;p&gt;Pragmatically though, I think security has to be an exception to this, but hopefully one that's made as transparent as possible to the application protocol.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Burrows</dc:creator><pubDate>Tue, 09 Jun 2009 16:27:23 -0000</pubDate></item><item><title>Re: Fomenting unREST : Is RESTfulness a semantics game ? Why does REST require statelessness ?</title><link>http://blog.dhananjaynene.com/2008/11/rest-fomenting-unrest-is-restfulness-a-semantics-game-why-does-rest-require-statelessness/#comment-442489621</link><description>&lt;p&gt;REST is stateless, meaning there is no session state tied to a particular client stored on the server. Session id / authorization token is something that you may not want to pass on as a part of the URI. I think the authentication part belongs to the header area.&lt;/p&gt;&lt;p&gt;Standard authentication mechanisms like Http Auth, OAuth can help achieve this. Another way of achieving this is by using cookies. The tricky thing with cookie is to make sure that the server validate the cookie with out session state. I read this piece recently on using digest with cookies on the REST-discuss group: &lt;a href="http://tech.groups.yahoo.com/group/rest-discuss/message/10909" rel="nofollow noopener" target="_blank" title="http://tech.groups.yahoo.com/group/rest-discuss/message/10909"&gt;http://tech.groups.yahoo.co...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Surya Suravarapu</dc:creator><pubDate>Sat, 04 Apr 2009 02:04:13 -0000</pubDate></item><item><title>Re: Fomenting unREST : Is RESTfulness a semantics game ? Why does REST require statelessness ?</title><link>http://blog.dhananjaynene.com/2008/11/rest-fomenting-unrest-is-restfulness-a-semantics-game-why-does-rest-require-statelessness/#comment-442489627</link><description>&lt;blockquote&gt;If you are providing a REST api then session id is not required.&lt;/blockquote&gt;&lt;p&gt; Agreed in principle. But the way I read REST, a purist approach would completely abhor session id, since that id typically is linked to some state on the server.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;blockquote&gt;There are many ways how we can implement a pure REST api for this particular case study. Eg. implementing REST version of oAuth to minimize sending critical info all the time and using smaller access tokens.&lt;/blockquote&gt;&lt;p&gt; Interesting. Would an oAuth access token be considered a id or a resource ? Not sure.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dhananjay Nene</dc:creator><pubDate>Fri, 03 Apr 2009 21:53:28 -0000</pubDate></item><item><title>Re: Fomenting unREST : Is RESTfulness a semantics game ? Why does REST require statelessness ?</title><link>http://blog.dhananjaynene.com/2008/11/rest-fomenting-unrest-is-restfulness-a-semantics-game-why-does-rest-require-statelessness/#comment-442489640</link><description>&lt;p&gt;First of all I am not sure if seesion id is required. If you are providing a REST api then session id is not required. There are many ways how we can implement a pure REST api for this particular case study. Eg. implementing REST version of oAuth to minimize sending critical info all the time and using smaller access tokens. But that is not the point.&lt;br&gt;Point you have raised is correct, sometimes being creator of a technology or architecture style (in this case) we tend to be too rigid about rules and regulation. the best we not so REST api providers can do is call it REST99 (99.9% pure REST) and leave it there.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sushrut Bidwai</dc:creator><pubDate>Fri, 03 Apr 2009 20:00:29 -0000</pubDate></item><item><title>Re: Fomenting unREST : Is RESTfulness a semantics game ? Why does REST require statelessness ?</title><link>http://blog.dhananjaynene.com/2008/11/rest-fomenting-unrest-is-restfulness-a-semantics-game-why-does-rest-require-statelessness/#comment-442489605</link><description>&lt;p&gt;Great article that delves into the practical side of the HATEOS debate.  Well done.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Davison</dc:creator><pubDate>Fri, 03 Apr 2009 17:49:14 -0000</pubDate></item></channel></rss>