Saturday, March 27, 2010

Hi, I test my post
Hi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my post
Hi, I test my post
Hi, I test my post

Hi, I test my post

Hi, I test my post
Hi, I test my post

Friday, January 1, 2010

REST vs SOAP ?

The main difference between these two approaches is the way that the service state is maintained. Do not think of the service state as the application or session state; instead, think of it as the different states that an application passes through during its lifetime. With SOAP, movement through different states can be accomplished through interaction with a single service endpoint, which may encapsulate and provide access to many operations and message types. With REST, a limited set of operations is allowed, and these operations are applied to resources represented and addressable by URIs (HTTP addresses). The messages capture the current or required state of the resource

+ SOAP is a protocol that provides a basic messaging framework upon which abstract layers can be built, and is commonly used as an RPC framework that passes calls and responses over networks using XML-formatted messages.

+ SOAP handles issues such as security and addressing through its internal protocol implementation, but requires a SOAP stack to be available.

+ REST is a technique that can utilize other protocols, such as JavaScript Object Notation (JSON), the Atom publishing protocol, and custom Plain Old XML (POX) formats.

+ REST exposes an application and data as a state machine, not just a service endpoint. It allows standard HTTP calls such as GET and PUT to be used to query and modify the state of the system. REST is stateless by nature, meaning that each individual request sent from the client to the server must contain all of the information necessary to understand the request since the server does not store
the session state data.