Comments on: Building RESTful Web Services http://www.ghidinelli.com/2008/11/20/building-restful-web-services Thu, 01 Jun 2017 18:51:00 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ben Nadel http://www.ghidinelli.com/2008/11/20/building-restful-web-services/comment-page-1#comment-52812 Ben Nadel Fri, 12 Dec 2008 15:17:08 +0000 http://www.ghidinelli.com/?p=320#comment-52812 Brett's presentation was awesome (I know this is an old post but it just started showing up on CFBloggers). I thought I had an understanding of what REST was... I was waaaay wrong :) Brett’s presentation was awesome (I know this is an old post but it just started showing up on CFBloggers). I thought I had an understanding of what REST was… I was waaaay wrong :)

]]> By: Brett http://www.ghidinelli.com/2008/11/20/building-restful-web-services/comment-page-1#comment-52425 Brett Tue, 25 Nov 2008 18:51:06 +0000 http://www.ghidinelli.com/?p=320#comment-52425 Hey Brian - I gave a presenation on building RESTful CF applications at the NYCFUG this summer, the resources are posted here if you want to check it out: http://www.nycfug.com/meetings/2008-06-10-Brett-On-RESTful-Web-Services.cfm I have a slide or two in there on content type negotiation... We use a URL parameter to specify the content type since we have not been able to not rely on the clients to implement the accepts header consistantly. Ideally though, the URL parameter would be used as an optional override to the HTTP header to provide support to clients that are not using Accepts correctly. Looking forward to seeing your follow up posts, I'm a huge REST fan. Lots of good info over at http://www.subbu.org/ too if you haven't seen it. cheers, .brett Hey Brian -

I gave a presenation on building RESTful CF applications at the NYCFUG this summer, the resources are posted here if you want to check it out:

http://www.nycfug.com/meetings/2008-06-10-Brett-On-RESTful-Web-Services.cfm

I have a slide or two in there on content type negotiation… We use a URL parameter to specify the content type since we have not been able to not rely on the clients to implement the accepts header consistantly. Ideally though, the URL parameter would be used as an optional override to the HTTP header to provide support to clients that are not using Accepts correctly.

Looking forward to seeing your follow up posts, I’m a huge REST fan. Lots of good info over at http://www.subbu.org/ too if you haven’t seen it.

cheers,

.brett

]]>