WCF RestFul Services

REpresentational State Transfer. History/Story- Introduced in 2000 by Roy Thomas Fielding as part of his doctoral research paper and soon after that it became quite popular because of its features and ease to use.
Currently many popular websites are using it likes of google, flickr.
In this blog will mention about the features of Restful services and how this use a different architectural approach toward creating webservices. We have SOAP architecture and other is REST, major difference SOAP is transport independent protocol while REST embrace HTTP.
# Rest based system are divided into resources and each resource can have multiple representational   e.g. Html, Xml, jpeg, flash and every resource has unique address(URI). e.g.

# You can perform operations on resources i.e. HTTP verbs GET,POST,PUT,DELETE and also  GET  can utilize web caching infrastructure.
# Rest service is stateless i.e. no client context stored on server, we don’t create proxies to consume.
# In Rest service we have flexibility over response structure, good choice to build when client is unknown.
# No metadata.

There are features in WCF 3.5 & in onwards .net frameworks that allow building REST-ful services:
1. Support for URIs.
2. Have services dispatcher for URI and verbs.
3. Support for JSON, RSS, atom , direct POX.
4. Response formatting.
5. Caching support in IIS.
6. ASP.NET routing integration.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s