Request–response
(Redirected from
Request-response
)In
client–server architectures.[1]
For simplicity, this pattern is typically implemented in a purely
timeout period expires. However, request–response may also be implemented asynchronously, with a response being returned at some unknown later time. When a synchronous system communicates with an asynchronous system, it is referred to as "sync over async" or "sync/async".[2] This is common in enterprise application integration (EAI) implementations where slow aggregations, time-intensive functions, or human workflow
must be performed before a response can be constructed and delivered.
In contrast, one-way computer communication, which is like the push-to-talk or "barge in" feature found on some phones and two-way radios, sends a message without waiting for a response. Sending an email is an example of one-way communication, and another example are fieldbus sensors, such as most CAN bus sensors, which periodically and autonomously send out their data, whether or not any other devices on the bus are listening for it. (Most of these systems use a "listen before talk" or other contention-based protocol so multiple sensors can transmit periodic updates without any pre-coordination.)
See also
- Futures and promises
- Message exchange pattern
- Publish/subscribe
- Remote procedure call
References
- ISBN 0-321-20068-3. p. 184
- ^ "Sync-over-Async Switch - IBM Business Process Management Products Support Blog Blog". IBM. 2009-10-20.