endpoint.tv - WCF AppFabric Caching Behavior Sample
- Posted: Dec 13, 2010 at 10:37 AM
- 3,971 Views
- 2 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
While I was out on holiday break I had this idea. What if you could create an operation behavior that would cache results for a WCF call and intercept the call returning the response from the cache if it was found? That would be pretty cool so I created the WCF AppFabric Caching Behavior Sample and on this episode I'll show you how it works.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Hi Ron
Really like this, thanks for posting, although I have to admit that when I thought about it, whilst watching the video, I've decided for me it would work better as a client endpoint behaviour, so that I can save the hit on the service endpoint completely; of course this is true in my case only because I am in control of all of the clients' endpoints and know they all have access to the cache...
Agreed - I wanted to make a client endpoint behavior but it turns out that you cannot intercept a call on the client. There are other ways to do this but they involve messing with the client proxy typically.
Remove this comment
Remove this thread
close