Comments on: A humble WCF feature request (or four) http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/ Sat, 12 Nov 2011 20:10:43 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Damian Mehers http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/comment-page-1/#comment-470 Damian Mehers Sat, 01 Nov 2008 00:29:22 +0000 http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/#comment-470 I've done something similar to what you are looking for, except that instead of having to have two methods (one for XML and one for JSON) you can have a single method, and depending on the content type that the client requests (via the "Accept" HTTP Request header), the appropriate format is automatically returned. I do it by hooking in my own IDispatchMessageFormatter All the code etc: http://damianblog.com/2008/10/31/wcf-rest-dynamic-response/ /Damian I’ve done something similar to what you are looking for, except that instead of having to have two methods (one for XML and one for JSON) you can have a single method, and depending on the content type that the client requests (via the “Accept” HTTP Request header), the appropriate format is automatically returned.

I do it by hooking in my own IDispatchMessageFormatter

All the code etc:
http://damianblog.com/2008/10/31/wcf-rest-dynamic-response/

/Damian

]]> By: Using WCF for REST, Part 3 « Infovark Underground http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/comment-page-1/#comment-96 Using WCF for REST, Part 3 « Infovark Underground Tue, 27 May 2008 15:45:00 +0000 http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/#comment-96 [...] the bit between the one forward slash and another, or one querystring parameter. A few bloggers requested more flexibility in UriTemplates, and the WCF team answered with the soon-to-be-released 3.5 SP1. The ability to define variables [...] [...] the bit between the one forward slash and another, or one querystring parameter. A few bloggers requested more flexibility in UriTemplates, and the WCF team answered with the soon-to-be-released 3.5 SP1. The ability to define variables [...]

]]> By: aaron http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/comment-page-1/#comment-94 aaron Wed, 22 Aug 2007 23:29:29 +0000 http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/#comment-94 Good thought - except that the ACCEPT header can specify wildcard values, which would not play well with the well-defined interfaces WCF offers. Besides, I think being explicit about encoding, etc. is a good thing - I just want to do it at the ServiceOperation level, not the endpoint binding level.<BR/><BR/>Your blog post has some good points about the UriTemplate limitations. I think I read that the limitations will get better over time, but can't find my source (might've been <A HREF="http://hyperthink.net/blog" REL="nofollow">Steve Maine's blog</A> Good thought – except that the ACCEPT header can specify wildcard values, which would not play well with the well-defined interfaces WCF offers. Besides, I think being explicit about encoding, etc. is a good thing – I just want to do it at the ServiceOperation level, not the endpoint binding level.

Your blog post has some good points about the UriTemplate limitations. I think I read that the limitations will get better over time, but can’t find my source (might’ve been Steve Maine’s blog

]]> By: Darrel Miller http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/comment-page-1/#comment-95 Darrel Miller Wed, 22 Aug 2007 23:29:29 +0000 http://www.aaronlerch.com/blog/2007/07/16/a-humble-wcf-feature-request-or-four/#comment-95 I'm not too sure about your first request to allow extensions in the Uri. Isn't the Accept HTTP header supposed to be used to indicate what type of media you want back? The fact that the average browser does not let you specify the Accept header directly shouldn't encourage to re-invent the wheel. <BR/>Having said that, if the UriTemplate allowed us to do<BR/>UriTemplate="/blog/tags/WCF{MediaType}" then it would not be a problem.<BR/>I do like your second suggestion though. The ability to apply an XSLT transform on the serialized return values would be excellent.<BR/>I posted a few weeks ago about a number of other limitations that I have come across with UriTemplate.<BR/>http://www.bizcoder.com/index.php/2007/07/24/systemuritemplate/ I’m not too sure about your first request to allow extensions in the Uri. Isn’t the Accept HTTP header supposed to be used to indicate what type of media you want back? The fact that the average browser does not let you specify the Accept header directly shouldn’t encourage to re-invent the wheel.
Having said that, if the UriTemplate allowed us to do
UriTemplate=”/blog/tags/WCF{MediaType}” then it would not be a problem.
I do like your second suggestion though. The ability to apply an XSLT transform on the serialized return values would be excellent.
I posted a few weeks ago about a number of other limitations that I have come across with UriTemplate.
http://www.bizcoder.com/index.php/2007/07/24/systemuritemplate/

]]>