SOAP-Based vs. RESTful Web Services: A Case Study for Multimedia Conferencing

Belqasmi, Fatna; Singh, Jashanjot; Melhem, Suhib Bani; Glitho, Roch

doi:10.1109/mic.2012.62

Cited by 41 publications

(16 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…So RESTful style services don't need SOAP or other application layer protocols, but only need HTTP. The case study in [8] shows that RESTful Web Service is more concise than SOAPbased Web Service, and even provides better performance. So RESTful is named lightweight SOA implementation technology.…”

Section: B Development From Soa To Edsoamentioning

confidence: 99%

An Event-driven Service-oriented Architecture for Internet of Things Service Execution

et al. 2015

View full text Add to dashboard Cite

Abstract-IoT (Internet of Things) bridges the physical world and information space. IoT services are environmentally sensitive and event-driven, so new IoT service architecture should adapt to these features. This paper analyses IoT sensing service characteristics and proposes future services architecture. It is focused on middleware architecture and interface presentation technology. In the middleware layer, traditional SOA architecture is insufficient in real-time response and parallel processes of service execution. This paper proposes a new sensing service system based on EDSOA (Event Driven SOA) architecture to support realtime, event-driven, and active service execution. At the presentation layer, this paper presents new IoT browser features, including using augmented reality technology for input and output and realizing the superposition of the physical world and abstract information. Through a use case and proof-of-concept implementation-road manhole cover monitoring system-we verified the feasibility of the proposed ideas and framework.

show abstract

Section: B Development From Soa To Edsoamentioning

confidence: 99%

An Event-driven Service-oriented Architecture for Internet of Things Service Execution

et al. 2015

View full text Add to dashboard Cite

show abstract

“…CREATE used for inserting record, READ for getting selected record, UPDATE for updating any existing record and DELETE for removing any record. [6] REST take advantage of these simple operations and use them efficiently than SOAP. For example, if we are willing to remove any record from back-end data (such as item with particular ID) then for REST we have to just call DELETE method with item's ID in URL which allows REST service to omit internal XML payload, which results in reducing its packet size.…”

Section: Overheadmentioning

confidence: 99%

“…REST does not restrict client-server communication to particular protocol but is most commonly used with HTTP. [6] REST web services are based on URLs and four HTTP methods that are POST (For insertion of new record), PUT (For updating any existing record), DELETE (For removing any existing record) and GET (For getting any record's information) [7].…”

Section: Introductionmentioning

confidence: 99%

Differentiating Parameters for Selecting Simple Object Access Protocol (SOAP) vs. Representational State Transfer (REST) Based Architecture

Khan¹,

Abbasi²

2015

JACN

View full text Add to dashboard Cite

“…These schemas help the receiver to correctly interpret the text. SOAP messages are taken by SOAP servers and they are interpreted so that as a result of that web servers become active and so their function [7,8].…”

Section: Soapmentioning

confidence: 99%