RESTful Authentication
I might be overcomplicating things, but I just don’t understand RESTful Authentication. I understand the focus on resources (noun) rather than actions (verbs), or at least I think understand this. However, in order for every resource to be uniquely addressable (via an URI), it seems necessary to include a authentication token in every URI (if merely to have a “you are logged in as john.doe|logout” link). This produces ugly, long, crufty URIs which no one likes. Furthermore, the requirement for RESTful applications to be entirely stateless may or may not eliminate the use of cookies (which render an application pseudo-stateful). Anyone want to point me to a good explanation of this?
