Messaging pattern: Difference between revisions

Content deleted Content added
Adding local short description: "Architectural pattern describing communication between systems", overriding Wikidata description "any architectural pattern describing communication between software systems or subsystems"
m SOAP: fixing grammar after special:diff/1079237165 on 25 March 2022
 
Line 29:
===SOAP===
The term ''message exchange pattern'' has an extended meaning within the '''Simple Object Access protocol''' ([[SOAP]]).<ref>http://www.w3.org/TR/soap12-part1/#soapmep SOAP MEPs in SOAP W3C Recommendation v1.2</ref><ref>[http://www.w3.org/TR/wsdl20-additional-meps/ Web Services Description Language (WSDL) Version 2.0: Additional MEPs<!-- Bot generated title -->]</ref> SOAP MEP types include:
#'''In-Only''': This is equivalent to ''one-way''. A standard one-way messaging exchange where the consumer sends a message to the provider that provides dodoes not send any type of response.
#'''Robust In-Only''': This pattern is for reliable one-way message exchanges. The consumer initiates with a message to which the provider responds with status. If the response is a status, the exchange is complete, but if the response is a fault, the consumer must respond with a status.
#'''In-Out''': This is equivalent to ''request–response''. A standard two-way message exchange where the consumer initiates with a message, the provider responds with a message or fault and the consumer responds with a status.