"A. Pagaltzis" <[EMAIL PROTECTED]> writes: > * Terrence Brannon <[EMAIL PROTECTED]> [2005-09-04 03:15]: >> To me, that means "no cookies". But your discussion of 401 and >> 403 would imply such a mechanism for recognizing who made the >> request? > > I do (still?) use cookies.
You are using a REST-inspired approach to web design, not pure REST: <quote src="http://www.prescod.net/rest/state_transition.html";> REST basically advises you choose between these two strategies: send all of the state back and forth (in this case using GET and URIs) or capture parts of the state as resources with URIs and transmit links to that state back and forth. What REST advises against is state without a URI name. COOKIES ARE AN EXAMPLE OF UN-REST-LIKE DATA. Cookes are implicit, so third parties have no access to them and even the client application will not typically have any way to know what cookies were in effect when a particular message was created hours ago. REST stands for REpresentational State Transfer - the constant transfer of state (or references to state) back and forth as representations are key to its design. </quote> -- Carter's Compass: I know I'm on the right track when, by deleting something, I'm adding functionality. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ cgi-prototype-users mailing list cgi-prototype-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cgi-prototype-users
