Terminology Glossary#
Message Direction Terminology#
This library uses client-perspective terminology to describe message flow, which differs from the official OUCH 5.0 specification terminology.
Client-Perspective Terminology (Used in This Documentation)#
Term |
Direction |
Description |
|---|---|---|
Egress Messages |
Client → Exchange |
Messages sent from your application to the exchange |
Ingress Messages |
Exchange → Client |
Messages received by your application from the exchange |
Official OUCH 5.0 Terminology (Exchange Perspective)#
Term |
Direction |
Description |
|---|---|---|
Inbound Messages |
Client → Exchange |
Messages sent from participant to OUCH host (inbound to exchange) |
Outbound Messages |
Exchange → Client |
Messages sent from OUCH host to participant (outbound from exchange) |
Mapping#
Egress Messages (client perspective) = Inbound Messages (official terminology)
Ingress Messages (client perspective) = Outbound Messages (official terminology)
Why Different Terminology?#
The official OUCH 5.0 specification uses terminology from the exchange’s perspective:
Messages coming into the exchange are “Inbound”
Messages going out from the exchange are “Outbound”
This library’s documentation uses client-perspective terminology for clarity:
Messages egressing from your application are “Egress”
Messages ingressing into your application are “Ingress”
References#
Official OUCH 5.0 specification uses “Inbound” and “Outbound” terminology
See Protocol Overview for protocol details
See Egress Messages for client→exchange message types
See Ingress Messages for exchange→client message types