Comments on: Why REST?

By: nickelcode » ASP.NET on Rails

nickelcode » ASP.NET on Rails — Tue, 18 Nov 2008 20:34:10 +0000

[...] Routes! I loves me some Routes! Making your web apps RESTful has many advantages (see here, and here for some examples) and in any case the flexibility that custom routes provides is [...]

By: What do people have against URLs? « Derivadow.com

What do people have against URLs? « Derivadow.com — Sun, 22 Jun 2008 21:21:12 +0000

[...] Elliotte Rusty Harold puts it, all resources are identified by URLs: Tagging distinct resources with distinct URLs enables bookmarking, linking, search engine storage, [...]

By: Links for 2008-06-18 - tonyscott.org.uk

Links for 2008-06-18 - tonyscott.org.uk — Wed, 18 Jun 2008 13:05:55 +0000

[...] Why REST? [The Cafes] [...]

By: links for 2008-06-15 « Derivadow.com

links for 2008-06-15 « Derivadow.com — Sun, 15 Jun 2008 18:30:37 +0000

[...] Why REST? Robust, scalable web applications work with HTTP rather than against it. [The Cafes] Resources should be identified by URLs. For example, each user should have a separate URL that links directly to their record, rather than all your customers sharing a single URL whose content changes depending on the value of some login cookie. (tags: architecture http programming rest) [...]

By: Tom Scott

Tom Scott — Sat, 14 Jun 2008 21:41:46 +0000

Good article. It drives me nuts that folk fail to think of personalization in terms of a RESTful architecture – and instead expect users to personalize at a URL.

By: website design

website design — Tue, 10 Jun 2008 14:43:57 +0000

So the lesson here is that you should design your application to conform to the architecture of the underlying protocol, rather than shoe-horning it into a form it is not? A shocking and revolutionary development, indeed!