Archives
-
Adding caching to WCF RESTful services using the REST Starter Kit
As promised, this is the first of a series of posts that intend to cover the new capabilities implemented in the WCF REST Starter Kit to enhance the development of RESTful services using WCF. Specifically, this post is focus on how to enable caching on RESTFul services by using the REST Starter Kit . Undoubtedly, caching is one of the greatest benefits of the Web programming model and one of the main attractive of REST over alternatives such as SOAP/WS-*. Throughout the evolution of the web, the industry has developed very innovative techniques for optimizing content retrieval by the use of caching. These techniques have been reflected in technologies such as MemCache, Oracle Coherence and more recently Microsoft's Velocity that specialized in distributed caching. Additionally, web technologies like ASP.NET provides generic programming models that address some of the most common caching scenarios. All this infrastructure and technologies can be naturally leveraged by RESTful services without the need of creating new caching mechanisms. Precisely, the REST Starter Kit leverages ASP.NET extending WCF RESTful services with caching capabilities.
-
Microsoft gives you more REST
Today Microsoft announced the first CTP of the WCF REST Starter Kit and the REST developer center. This technology package includes a set of guidances, project templates and extensibility components that complement the existing features of WCF 3.5 in terms of RESTful services. Essentially, this packages addresses important aspects of real world RESTful scenarions such as caching, exception handling or security. I have been playing with this technology for a few weeks now and I am really excited about it. I will be blogging some of my thoughts and examples in the upcoming days.
-
Tim recommends learning dynamic languages
Check out his reasooning here
-
Web Services Federation Patterns: The Attribute Service
-
Configuring the BAM WCF interceptor programmatically
Although adding the BAM WCF-WF interceptors via .config files works for most of the scenarios, there are some cases on which you need to add these interceptors programmatically. Dealing with multiple BAM databases, dynamically enabling and disabling tracking and dynamically adjusting the polling intervals are some of the most common reasons for not relying 100% on the app.config configuration.
-
New REST "must read" papers