REST in WCF - Part VII (HI-REST - Implementing Insert and Update)

REST in WCF Blog Series Index

Demystifying The Code — Thu, 07 Aug 2008 21:03:31 GMT

As some of you know, I am in the midst of a blog series on REST in WCF. Further, I have been hard at

REST in WCF - Part XI (Tunneling PUT through POST)

Demystifying The Code — Tue, 11 Nov 2008 01:26:08 GMT

A common scenario you may encounter when designing your RESTful services is supporting clients that only

REST in WCF

Journal of Abu Sayed Mohammad Ismail — Wed, 24 Dec 2008 09:34:43 GMT

The series blog post on REST in WCF REST in WCF - Part I (REST Overview) REST in WCF - Part II (AJAX

re: REST in WCF - Part VII (HI-REST - Implementing Insert and Update

samtadsh — Fri, 13 Feb 2009 23:24:35 GMT

Hi Rob,

You have put together a very useful set of blogs... thanks.

I tried out the starter solution you put out. After I do an Update or Insert, the database gets updated. But the part which re-populates the drop-down control with the products list never gets updated. It looks like GetProductGrouping doesn't get invoked after an Update/Insert operation or somewhere the previous product list is cached.

Did you encounter this when you try out the sample application?

re: REST in WCF - Part VII (HI-REST - Implementing Insert and Update

rob.bagby — Fri, 13 Feb 2009 23:42:55 GMT

Not sure which version you have (as I have released a few). The issue you are seeing has to do with caching. One solution would be to put a no cache directive on the get like the following:

//Tell the client not to cache

outResponse.Headers.Add("Cache-Control", "no-cache");

You have to get a ref to the response which is available in the WebOperationContext.Current.

Rob