Skip to content

Commit 811a647

Browse files
committed
add sequence diagram
1 parent 7713ea0 commit 811a647

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/RedisQueue.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,13 @@ At a high level steps the Redis Queue goes through to execute an RPC are:
5959
9. Client B sends the request to the tentacle, waits for the response, and calls `ApplyResponse()` with the ResponseMessage.
6060
10. Client B writes the `ResponseMessage` to redis in a hash using the `GUID` as the key.
6161
11. Client B Pulses the `ResponseMessage channel` keyed by the RequestMessage `GUID`, that a Response is available.
62-
12. Client A receives a pulse on the `ResponseMessage channel` and so knows a Response is available, it reads the response from Redis and returns from the `QueueAndWait()` method.
62+
12. Client A receives a pulse on the `ResponseMessage channel` and so knows a Response is available, it reads the response from Redis and returns from the `QueueAndWait()` method.
63+
64+
### Flow Diagram
65+
66+
The following sequence diagram illustrates this high-level flow:
67+
68+
![Redis Queue Solution Flow](images/redis-queue-flow-diagram.svg)
6369

6470
## Cancellation support.
6571

0 commit comments

Comments
 (0)