Skip to main content

WCF REST versioning, JSON and Dynamic objects

As everyone knows JSON is a very light weight form of transport when it comes to the web, you can respond and consume JSON using WCF REST services, I have blogged about this in one of my earlier posts in 2008, but last month I got to work on this...
WCF makes things very easy, if the client sends a JSON formatted string, WCF infrastructure will de-serialize this into a custom type that you have specified in your operation contract.
For an example...

[WebInvoke(Method="POST"....)]
public void Save(Student student){}

so if you send a JSON string like this on your POST body
{Name : "Nairooz Nilafdeen", Age : 26}
...the WCF infrastructure will de-serialize the JSON string into the Student object (as long as the JSON key-value matches the properties in the Student type)..

Now, the problem with this approach is when you send a JSON string that contains an additional property that is not available in the Student class, now WCF will not be able to de-serialize as the JSON string does no exactly match with the Student type.

In a few situation you want to keep one simplified API that users would want to access, but how do you take versioning into account?
The simplest way would be to except a stream into your operation, so now it becomes like this...

[WebInvoke(Method="POST"....)]
public void Save(Stream stream){}

(you can alternativley make 2 URLs available for differen versions...)
Now all the client needs to do is send any version of the Student type but also send the version of the service it's using in the header..on the service side you would look at the header and according to the version you will fill in the correct version of the Student type...
but, now the issue is that you are getting a JSON stream, now you need to read this and get the correct values for the stream...

Let .Net dynamic do the talking, you can use the DynamicJson library available at codeplex (google it...)and you can do this...

dynamic jsonObject = DynamicJson.Parse(stream);

you can access the Name property of the JSOn stream like this...

string name = jsonObject.Name;

and whats more interesting is when you are creating a unit test to test out this API...
simply create a ExpandoObject (another dynamic object) and just keep on filling what you need, no need to create a static class...

ExpandoObject obj = new ExpandoObject();
obj.Name = "Nairooz Nilafdeen";

I know the post is not really concise, but noting it down for my future use.


Comments

Post a Comment

Popular posts from this blog

Hosting WCF services on IIS or Windows Services?

There came one of those questions from the client whether to use II7 hosting or windows service hosting for WCF services. I tried recollecting a few points and thought of writing it down. WCF applications can be hosted in 2 main ways - In a Windows service - On IIS 7 and above When WCF was first released, IIS 6 did not support hosting WCF applications that support Non-HTTP communication like Net.TCP or Net.MSMQ and developers had to rely on hosting these services on Windows Services. With the release of IIS 7, it was possible to deploy these Non-Http based applications also on IIS 7. Following are the benefits of using IIS 7 to host WCF applications Less development effort Hosting on Windows service, mandates the creating of a Windows service installer project on windows service and writing code to instantiate the service, whereas the service could just be hosted on IIS by creating an application on IIS, no further development is needed, just the service implementa
4 comments
Read more

The maximum nametable character count quota (16384) has been exceeded

Some of our services were growing and the other day it hit the quote, I could not update the service references, nor was I able to run the WCFTest client. An error is diplayed saying " The maximum nametable character count quota (16384) has been exceeded " The problem was with the mex endpoint, where the XML that was sent was too much for the client to handle, this can be fixed by do the following. Just paste the lines below within the configuration section of the devenve.exe.config and the svcutil.exe.config files found at the locations C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE , C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin Restart IIS and you are done. The detailed error that you get is the following : Error: Cannot obtain Metadata from net.tcp://localhost:8731/ Services/SecurityManager/mex If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. F
5 comments
Read more

ASP.NEt 2.0 Viewstate and good practices

View state is one of the most important features of ASP.NET because it enables stateful programming over a stateless protocol such as HTTP. Used without strict criteria, though, the view state can easily become a burden for pages. Since view state is packed with the page, it increases size of HTTP response and request. Fortunately the overall size of the __VIEWSTATE hidden field (in ASP.NET 2.0) in most cases is as small as half the size of the corresponding field in ASP.NET 1.x. The content of the _VIEWSTATE field (in client side) represent the state of the page when it was last processed on the server. Although sent to the client, the view state doesn't contain any information that should be consumed by the client. In ASP.NET 1.x, if you disable view state of controls, some of them are unable to raise events hence control become unusable. When we bind data to a grid, server encodes and put whole grid in to view state, which will increase size of view state (proportional to the
Post a Comment
Read more