- Web Services Testing with soapUI
- Charitha Kankanamge
- 186字
- 2021-08-05 18:39:23
Message exchanging patterns
As we have already discussed, the web services communicate with each other and the other programs by sending messages. If we consider two SOAP processing nodes, the communication pattern between the two entities can be defined as a message exchanging pattern (MEP). The primary message exchanging patterns are:
- Request-response
- Fire and forget
In a request-response pattern, when a source entity (service requester) transmits a message to a destination (service provider), the provider should respond to the requester. This is the most commonly used message exchanging pattern and we will use this in most of the examples in this book.
In the following diagram, a service requester sends a SOAP request message to a service provider:

Upon receiving the SOAP request message, the service provider responds with a SOAP response as shown in the following diagram:

When a response to a request message is not expected from a web service (or service provider), it is known as a fire and forget message exchange pattern. For example, if we send a ping request to a web service, we do not expect a response message back.
- MySQL高可用解決方案:從主從復制到InnoDB Cluster架構
- Python數據分析入門:從數據獲取到可視化
- 大數據可視化
- Game Development with Swift
- 文本數據挖掘:基于R語言
- 新型數據庫系統:原理、架構與實踐
- Hadoop大數據實戰權威指南(第2版)
- Hands-On Mathematics for Deep Learning
- 新基建:數據中心創新之路
- Python數據分析與挖掘實戰(第3版)
- Chef Essentials
- 區塊鏈技術應用與實踐案例
- 聯動Oracle:設計思想、架構實現與AWR報告
- R Machine Learning Essentials
- 數據挖掘競賽實戰:方法與案例