Representational State Transfer or Rest services in WCF Windows Communication Foundation is the way of making services by which it is accessed by any platform
We make Rest services because it has a feature of getting communicated with any platform whether its IOS whether its Android or whether its on a other Operating System
For serving different Operating System with the same service we create Rest service for that
Client–server
Client Server can be on the separate compatibility type doesn't matter for the service unless interface between them gets changed.
Stateless
The client–server communication is further constrained by no client context being stored on the server between requests.
Cacheable
The request or the response while making any operation is stored for the future reference.
Layered system
Communication will always follow a layered system.
Code on demand (optional)
The code required at the time of making request or providing response will be provided as demanded by the user.
Uniform interface
The uniform interface constraint is fundamental to the design of any REST service.The four constraints for this uniform interface are
Identification of resources
The URL for making request or for providing response will be tracked and identified for the identification purpose.
Manipulation of resources through these representations
Self-descriptive messages
Every message includes sufficient information to narrate how to process the message.
0 Comment(s)