Patterns of Enterprise Application Architecture
Patterns of Enterprise Application Architecture
Caching XML Web Services for Mobility
Queue - Wireless
Java RMI, RMI tunneling and Web services comparison and performance analysis
ACM SIGPLAN Notices
LYE: A High-Performance Caching SOAP Implementation
ICPP '04 Proceedings of the 2004 International Conference on Parallel Processing
Understanding SOA with Web Services (Independent Technology Guides)
Understanding SOA with Web Services (Independent Technology Guides)
Performance evaluation of middleware bridging technologies
ISPASS '00 Proceedings of the 2000 IEEE International Symposium on Performance Analysis of Systems and Software
IEEE Internet Computing
Restful web services vs. "big"' web services: making the right architectural decision
Proceedings of the 17th international conference on World Wide Web
Demystifying RESTful Data Coupling
IEEE Internet Computing
Restful web services
Efficient Web Services in Mobile Networks
ECOWS '08 Proceedings of the 2008 Sixth European Conference on Web Services
Developing adapters for web services integration
CAiSE'05 Proceedings of the 17th international conference on Advanced Information Systems Engineering
RESTify: from RPCs to RESTful HTTP design
Proceedings of the Third International Workshop on RESTful Design
| Hi-index | 0.00 |
A protocol adapter ideally suited to enable enterprises to gradually transition from SOAP Web Services to RESTful HTTP Web Services without impacting existing clients is presented in this paper. The inherent advantage of such a transition is the visibility of RESTful HTTP messages to Web intermediaries such as caches. In contrast, SOAP messages are opaque, which disables Web intermediaries. While both approaches can use HyperText Transfer Protocol (HTTP) for message transfer, the paradigms contrast sharply. SOAP uses an interface specific approach whereas RESTful HTTP uses a Uniform Interface approach. SOAP marks up its payload with eXtensible Markup Language (XML) whereas in certain situations RESTful HTTP requires no XML. We present the disadvantages of the SOAP approach and outline how the RESTful HTTP approach solves these issues. We present results showing opaque SOAP messages transformed into transparent RESTful HTTP messages. We present StoRHm (SOAP to RESTful HTTP mapping), a protocol adapter which maps SOAP messages to RESTful HTTP format.