Thursday, August 23, 2007

If you want to use the [WebGet]/[WebInvoke] programming model in WCF, you need an endpoint with the right binding and the right endpoint behavior.

The binding is the out-of-the-box WebHttpBinding. The endpoint behavior can be either WebHttpBehavior or WebScriptEnablingBehavior.

What's the difference between the two?

The WebHttpBehavior is a general-purpose behavior that supports UriTemplate dispatch and POX/JSON/byte stream formats on the wire. Use it for general purpose HTTP/REST/Web-Style services.

The WebScriptEnablingBehavior is a "profile" of the WebHttpBehavior functionality designed specifically for interop with ASP.NET AJAX clients. It adds in some AJAX-isms like the ability to automatically generate ASP.NET AJAX client proxies.

Thursday, August 23, 2007 9:29:31 AM (Pacific Standard Time, UTC-08:00)  #    Comments [3]
Tuesday, September 04, 2007 2:37:41 PM (Pacific Standard Time, UTC-08:00)
steve thanks for you informations.
will try out it sometimes.
Monday, September 17, 2007 8:54:38 PM (Pacific Standard Time, UTC-08:00)
I have an off topic question; the other day I wrote a WCF application in aspnetcompatibilitymode=”true” and if I made a request via my asp.net project the WCF would see the cache, but if I made the same request via a forms application the WCF application would not see the cache. I know this is a bit off topic from your post, but what do you think?
Best regards,
Sean Gahan
http://seangahan.net
Monday, October 15, 2007 2:03:12 PM (Pacific Standard Time, UTC-08:00)
Hi Steve,
I'm spend the better part of today trying to get a restful service running using WCF on the ASP.net cassini web server. But I keep running into different problems. I'm trying to create a sample similar to the one you demonstrated at Mix07 working. Do you know of a sample somewhere that demonstrates restful services using WebGet and UriTemplate running on Cassini?
Thanks

Matt
Matt
Comments are closed.