Reading
Add Comment
REST is an architectural style to design systems like the Web.In a REST system, addresses identify things, not formats.
NOT REST
Rest:
Rest is not a protocol ,but a archtectural style that describe how system can share state(commuicate) with other system.
State are represent by json,xml
Most used protocol that use restful archtecture is HTTP
NOT REST
- browser: /showTodoList.php?format=html
- application: /showTodoList.php?format=json
Rest:
Rest is not a protocol ,but a archtectural style that describe how system can share state(commuicate) with other system.
State are represent by json,xml
Most used protocol that use restful archtecture is HTTP
- browser: “I want /todolists/7/, please give me HTML.”
- application: “I want /todolists/7/, please give me JSON.”
- SOAP is a protocol. REST is an architectural style.
- SOAP stands for Simple Object Access Protocol. REST stands for REpresentational State Transfer.
- SOAP can't use REST because it is a protocol. REST can use SOAP web services because it is a concept and can use any protocol like HTTP, SOAP.
- SOAP uses services interfaces to expose the business logic. REST uses URI to expose business logic.
- In Java JAX-WS is the java API for SOAP web services. In Java JAX-RS is the java API for RESTful web services.
- SOAP defines standards to be strictly followed. REST does not define too much standards like SOAP.
- SOAP requires more bandwidth and resource than REST. REST requires less bandwidth and resource than SOAP.
- SOAP defines its own security. RESTful web services inherits security measures from the underlying transport.
- SOAP permits XML data format only. REST permits different data format such as Plain text, HTML, XML, JSON etc.
- SOAP is less preferred than REST. REST more preferred than SOAP.
- REST is protocol independent. It's not coupled to HTTP. Pretty much like you can follow an ftp link on a website, a REST application can use any protocol for which there is a standardized URI scheme.
0 comments:
Post a Comment