Comments on: REST in IIS http://codepoetics.com/poetix/2004/11/04/rest-in-iis/ mocking the ways of true grown men Sat, 06 Mar 2010 04:10:06 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Blogmarks « michelc Blog http://codepoetics.com/poetix/2004/11/04/rest-in-iis/comment-page-1/#comment-11085 Blogmarks « michelc Blog Wed, 04 Oct 2006 21:35:27 +0000 http://codepoetics.com/poetix/?p=19#comment-11085 [...] REST in IIS [...] [...] REST in IIS [...]

]]> By: Dominic http://codepoetics.com/poetix/2004/11/04/rest-in-iis/comment-page-1/#comment-27 Dominic Thu, 04 Nov 2004 14:37:23 +0000 http://codepoetics.com/poetix/?p=19#comment-27 There is a kind of sweet spot where you can get a set of RESTful web services to double up as a browsable user interface, for instance by translating XML-formatted server responses into HTML with XSLT. On the other hand, there are things HTTP can do that most browsers don't do (like POST raw binary data or an XML document instead of a set of form fields). Of course that's changing now, as web applications like GMail start talking directly to servers from inside the browser, updating the contents of the page via scripting instead of having to refresh the complete page (or a frame) every time something changes. I wonder what percentage of web developers are aware of the difference between POST and PUT? There is a kind of sweet spot where you can get a set of RESTful web services to double up as a browsable user interface, for instance by translating XML-formatted server responses into HTML with XSLT. On the other hand, there are things HTTP can do that most browsers don’t do (like POST raw binary data or an XML document instead of a set of form fields).

Of course that’s changing now, as web applications like GMail start talking directly to servers from inside the browser, updating the contents of the page via scripting instead of having to refresh the complete page (or a frame) every time something changes.

I wonder what percentage of web developers are aware of the difference between POST and PUT?

]]> By: Francis Irving http://codepoetics.com/poetix/2004/11/04/rest-in-iis/comment-page-1/#comment-26 Francis Irving Thu, 04 Nov 2004 14:20:38 +0000 http://codepoetics.com/poetix/?p=19#comment-26 This bit is interesting: POST File to /Job_ID, status=201, location= /Job_ID/File_ID Amazing HTTP has a Created status code, and redirects you to the new resources. Not something you see used every day by web browsers. This bit is interesting:
POST File to /Job_ID, status=201, location= /Job_ID/File_ID

Amazing HTTP has a Created status code, and redirects you to the new resources. Not something you see used every day by web browsers.

]]> By: Dominic http://codepoetics.com/poetix/2004/11/04/rest-in-iis/comment-page-1/#comment-25 Dominic Thu, 04 Nov 2004 12:21:49 +0000 http://codepoetics.com/poetix/?p=19#comment-25 Well, yes. It is like a subset of WebDAV (without the additional HTTP verbs). The main difference is that job and file IDs are allocated by the server (whereas with MKCOL you tell the server what URL you want for your collection). The point is to ensure that CreateJob creates a new, unique URL, and for the client not to have to keep track of what URLs have been used before. Well, yes. It is like a subset of WebDAV (without the additional HTTP verbs).

The main difference is that job and file IDs are allocated by the server (whereas with MKCOL you tell the server what URL you want for your collection). The point is to ensure that CreateJob creates a new, unique URL, and for the client not to have to keep track of what URLs have been used before.

]]> By: Francis Irving http://codepoetics.com/poetix/2004/11/04/rest-in-iis/comment-page-1/#comment-24 Francis Irving Thu, 04 Nov 2004 12:09:25 +0000 http://codepoetics.com/poetix/?p=19#comment-24 All your file operations are beginning to look like WebDAV :) All your file operations are beginning to look like WebDAV :)

]]>