Both SOAP and REST are HTTP-based protocols designed to allow an application to access another through a defined API. SOAP is "strongly typed" compared to REST, and has a WSDL that allows a program (usually an IDE) to discover what methods and parameters are supported. However, SOAP is XML-based, while REST normally uses JSON (but can use XML), the result of which means smaller messages, more suited for mobile and slower networks, requiring less CPU power, memory, and bandwidth. Even REST+XML requires less bandwidth than SOAP, because even the headers in SOAP are in XML. Usually, you will use REST if you are developing for a mobile platform or in JavaScript, and SOAP if you are using a modern language that prefers SOAP (such as PHP).
Both SOAP and REST are HTTP-based protocols designed to allow an application to access another through a defined API. SOAP is "strongly typed" compared to REST, and has a WSDL that allows a program (usually an IDE) to discover what methods and parameters are supported. However, SOAP is XML-based, while REST normally uses JSON (but can use XML), the result of which means smaller messages, more suited for mobile and slower networks, requiring less CPU power, memory, and bandwidth. Even REST+XML requires less bandwidth than SOAP, because even the headers in SOAP are in XML. Usually, you will use REST if you are developing for a mobile platform or in JavaScript, and SOAP if you are using a modern language that prefers SOAP (such as PHP).
In REST, each unique URL is a representation of some object (with some ID). REST provides true “Web services” based on URIs and HTTP. While SOAP brings it’s own protocol and focuses on exposing pieces of application logic (not data) as services. SOAP exposes operations means that SOAP is focused on accessing named operations, each implement some business logic through different interfaces.
Both SOAP and REST are HTTP-based protocols designed to allow an application to access another through a defined API. SOAP is "strongly typed" compared to REST, and has a WSDL that allows a program (usually an IDE) to discover what methods and parameters are supported. However, SOAP is XML-based, while REST normally uses JSON (but can use XML), the result of which means smaller messages, more suited for mobile and slower networks, requiring less CPU power, memory, and bandwidth. Even REST+XML requires less bandwidth than SOAP, because even the headers in SOAP are in XML. Usually, you will use REST if you are developing for a mobile platform or in JavaScript, and SOAP if you are using a modern language that prefers SOAP (such as PHP).
All Answers
Hi
Soap Api - it uses authentication with username and password and communicationg with xml messages.
Rest Api - it uses http callout and token authentication used OAuth protocol. it is light weight and works well in mobile applications.
http://wiki.developerforce.com/page/REST_API
http://www.salesforce.com/us/developer/docs/api/index.htm
Both SOAP and REST are HTTP-based protocols designed to allow an application to access another through a defined API. SOAP is "strongly typed" compared to REST, and has a WSDL that allows a program (usually an IDE) to discover what methods and parameters are supported. However, SOAP is XML-based, while REST normally uses JSON (but can use XML), the result of which means smaller messages, more suited for mobile and slower networks, requiring less CPU power, memory, and bandwidth. Even REST+XML requires less bandwidth than SOAP, because even the headers in SOAP are in XML. Usually, you will use REST if you are developing for a mobile platform or in JavaScript, and SOAP if you are using a modern language that prefers SOAP (such as PHP).
In REST, each unique URL is a representation of some object (with some ID). REST provides true “Web services” based on URIs and HTTP. While SOAP brings it’s own protocol and focuses on exposing pieces of application logic (not data) as services. SOAP exposes operations means that SOAP is focused on accessing named operations, each implement some business logic through different interfaces.