Comments on: REST: the quick pitch https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/ Open information and technology. Sat, 23 Aug 2014 17:05:38 +0000 hourly 1 http://wordpress.com/ By: Tiger frank https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-4053 Thu, 16 Feb 2012 07:01:58 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-4053 I’m sorry, but
http://www.example.org/systems/foo/components/bar/
is way less self explaining than
http://www.example.org/get-component.asp?system=foo&component=bar

What is http://www.example.org/systems/foo/bar/components/
Only the developer knows, what he meant.

I also think the risk of unintentional overwriting should be minimized by authorisation, not by syntax.

]]> By: Distributed Weekly 117 — Scott Banwart's Blog https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-3934 Fri, 26 Aug 2011 14:25:17 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-3934 […] REST: the quick pitch […]

]]> By: links for 2011-07-04 – Kevin Burke https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-3869 Tue, 05 Jul 2011 00:04:14 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-3869 […] REST: the quick pitch | Quoderat some notes on how to do REST Jul 4th, 2011 by kevin. ← links for 2011-07-01 […]

]]> By: sideline.ca » Elevator pitch for REST https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-664 Tue, 10 Apr 2007 03:18:23 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-664 […] “REST: the quick pitch” is another good article to read if you’re trying to wrap your head around REST. It comes complete with an elevator pitch: With REST, every piece of information has its own URL. […]

]]> By: New JSR to define a high-level REST API for Java « Noelios Consulting https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-663 Tue, 03 Apr 2007 13:21:26 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-663 […] David Megginson (SAX, XML) […]

]]> By: Jim Davis https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-662 Wed, 14 Mar 2007 01:13:51 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-662 I agree with “Avoid scripting-language file extensions” but not the first reason you give for it. Attempting to conceal your framework is illusory protection at best, it’s “security through obscurity”. Your second reason is sufficient: it’s just encapsulation. Choice of scripting language or framework is an implementation detail that should not be reflected in the URL.

]]> By: bugfox blog » Blog Archive » David Megginson on REST https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-661 Mon, 12 Mar 2007 18:40:49 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-661 […] David Megginson offers a funny but insightful summary of the most important ideas in REST: The Quick Pitch: […]

]]> By: Pete Lacey's Weblog https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-660 Mon, 05 Mar 2007 18:35:41 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-660 Are you getting sound advice?

If you’re trying to get your arms around this whole REST thing, then the RESTian posts of the last few weeks have made that job a whole lot easier.
David Meggison starts things off with REST: the quick pitch. Including this wonderful elevator pi…

]]> By: pwb https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-659 Sat, 03 Mar 2007 05:34:11 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-659 I’m not totally sold on getting rid of querystrings. Querystrings have some advantages including being accessed from s and offering a bit of implicit description.

Which is better?

http://shoes.com/shoes/air-jordan/white/large
http://shoes.com/shoes?style=air-jordan&color=white&size=large

]]> By: pwb https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-658 Sat, 03 Mar 2007 00:56:16 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-658 I’mnot totally sold on getting rid of querystrings. They have some advantages. A major one is being accessible via s. Another is that they provide a bit of self description.

Which is better?

http://www.books.com/books/isbn/10231234234
http://www.books.com/books?isbn=10231234234

]]> By: John Nilsson https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-657 Thu, 01 Mar 2007 18:56:37 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-657 If the net/web ever transform to something passing blocks of data rather than packets between end-points (kind of like distributed hash table-overlay networks of today) I guess URN, resolved to SHA identifiers for a suitable representation by some google-like service who parses RDF webs, would be better than direct SHAs.

]]> By: BillG https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-656 Tue, 27 Feb 2007 00:36:56 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-656 Great post.

I’m glad that you said “_Try_ to avoid request parameters” (empahasis on try), since I see this as an example of where the ideals of REST taken to the extreme would make life a real pain in the ass. I “try” to do this when desining REST protocols, but only up to a certain point. Query strings are a practical convenience and are so broadly supported that to force every URL to be in the form /foo/bar/foo2/bar2/abc/def would just make things a lot harder than they need to be (for both clients and servers).

]]> By: ebyblog » Blog Archive » Bookmarks for February 17th through February 21st https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-655 Thu, 22 Feb 2007 00:31:43 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-655 […] Megginson Technologies: Quoderat » Blog Archive » REST: the quick pitch – With REST, every piece of information has its own URL. […]

]]> By: protocol7 » Blog Archive » links for 2007-02-17 https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-654 Sat, 17 Feb 2007 12:17:44 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-654 […] REST: the quick pitch (tags: rest HTTP by:david_megginson) […]

]]> By: Stefan Tilkov https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-653 Sat, 17 Feb 2007 08:31:50 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-653 Very nice, but I disagree with your description of POST and PUT. While POST can do lots of things, it should be used to create when PUT is available, and PUT should be used for updates.

]]> By: Pete Lacey https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-652 Sat, 17 Feb 2007 00:10:16 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-652 Actually, I know what URNs are (and in fact kinda like ’em for namespace names, that or URLs pointing to RDDL documents). I was wondering what use they would have in a RESTian world outside of that?

]]> By: david https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-651 Fri, 16 Feb 2007 18:16:39 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-651 Pete:

Your question “how would you dereference it” was exactly what killed URNs in the end (or at least put them into a permanent coma). They were a big deal in the late 1990s among the web technorati, who wanted to give us identifiers that were not subject to the whims of DNS (for example, you could give an ISBN-based URN to identify a book, instead of the Amazon link), but nobody ever figured out how they would actually work. Since the XML spec was written at that time, it retains the oddity that a system identifier (such as the external DTD subset) can be a URN reference as well as a URL reference, though I’m not sure what most XML parsers would do if they ever ran across something like this:

<!DOCTYPE foo SYSTEM "urn:newsml:megginson.com:20070216:foo-dtd:1">

<foo>Hello, world!</foo>
]]> By: Paul Downey https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-650 Fri, 16 Feb 2007 17:12:12 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-650 Love it!
I hate URNs too.

Content-negotiation may come into its own yet, especially with something like yadis for OpenID, but suffixes are ok, so long as they’re the format being returned, not the authoring tool – i.e. .xml, .json, .html is fine, .php, .pl, .asp, .asmx sucks. Much better than ?format=json as seen in Yahoo! services, anyway.

]]> By: Pete Lacey https://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/#comment-649 Fri, 16 Feb 2007 15:44:46 +0000 http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-649 Very nice summary. Quick question, though. Who’s advocating the use of URNs? In what context? If you were to use URNs to name a resource, how would you dereference it? Sorry, but I haven’t seen this bit of perceived wisdom before.

]]>