China
Africa
Explore chapters and articles related to this topic
Web Services for Embedded Devices
Published in Richard Zurawski, Industrial Communication Technology Handbook, 2017
Vlado Altmann, Hendrik Bohn, Frank Golatowski
The pure SOAP has a strong binding to HTTP for historical reasons although meant to be transport protocol independent. This results in the disadvantage that the address of targeted services can only be found in the HTTP header and only synchronous messaging is supported. Message routing depends on HTTP, and publish/subscribe patterns are not supported. WS-Addressing remedies these deficiencies by specifying mechanisms to address WS and messages in a transport-neutral way [15]. SOAP messages can be sent over multiple hops and heterogeneous transport protocols in a consistent manner. Furthermore, it allows sending responses to a third party (WS or WS client). WS-Addressing introduces the concepts of EPRs and message information (MI) header, which are included into the SOAP header.
Web Services
Published in John Footen, Joey Faust, The Service-Oriented Media Enterprise, 2012
In addition to being dynamic and extensible (as shown in Fig. 5-19), Web services are a standardized addition to the TCP stack, and that means it works over everything from dedicated, carrier-class networks to theoretically dial-up connections. No special infrastructure is needed to support the bulk of an enterprise's Web services needs. Using the right level of messaging security, Web services calls could travel over the public Internet with the same level of reliability that they travel within an enterprise. This means that geographically dispersed facilities benefit from using Web services as a communication protocol. Even in situations where the physical separation between two services might not be much but their organizational separation prevents the establishment of a dedicated communication channel, Web services can come to the rescue. Using extensions such as WS-Addressing, WS-Reliability, or WS-Security allows you to send messages over unreliable or insecure networks as though they were dedicated links.
A Multilayered Clustering Framework to build a Service Portfolio using Swarm-based algorithms
Published in Automatika, 2019
I. R. Praveen Joe, P. Varalakshmi
The following are the sources of the metadata of a web service XML Schema – For defining data types and structures.WSDL – For defining messages, message exchange patterns, interfaces and endpoints.WS-Policy – For declaring assertions for various qualities of service requirements, such as reliability, security, and transactions.WS-Addressing – For defining Web service endpoint references and associated message patterns.WS-MetadataExchange – For dynamically accessing XML, WSDL, and WS-Policy metadata when required.