This is the most common messaging pattern, also called request-reply. It has good
support from a large amount of middleware. It is the equivalent of a one way pull and
two way message exchange pattern (MEP) in terms of functionality and capability. It
can be implemented either synchronously or asynchronously. When implemented
asynchronously if the time between the request and response is significant, a separate
signal message can be used to confirm the receipt of the request message.
|
|
difi:metaLevel | undefined |
dct:type | archi:resource |
difi:namespace | - |
difi:abstractionLevel | undefined |
difi:language | no |
difi:name_no | Mønster for forespørsel-respons |
difi:name_en | Two-Way Request-Response Pattern (pull) |
difi:description_no | This is the most common messaging pattern, also called request-reply. It has good
support from a large amount of middleware. It is the equivalent of a one way pull and
two way message exchange pattern (MEP) in terms of functionality and capability. It
can be implemented either synchronously or asynchronously. When implemented
asynchronously if the time between the request and response is significant, a separate
signal message can be used to confirm the receipt of the request message. |
difi:description_en | |
label | ${name} |
difi:notes | |