From 1b46549ec44e8fa945cb3e15b0232c3ba44de66b Mon Sep 17 00:00:00 2001 From: David Fowler Date: Thu, 29 Nov 2018 10:13:09 -0800 Subject: [PATCH] Specify invocation ids are unique per connection (#4316) Make it clear that invocation ids are unique per connection --- src/SignalR/specs/HubProtocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/SignalR/specs/HubProtocol.md b/src/SignalR/specs/HubProtocol.md index cd9523de03..448a938740 100644 --- a/src/SignalR/specs/HubProtocol.md +++ b/src/SignalR/specs/HubProtocol.md @@ -72,7 +72,7 @@ There are three kinds of interactions between the Caller and the Callee: In order to perform a single invocation, the Caller follows the following basic flow: -1. Allocate a unique `Invocation ID` value (arbitrary string, chosen by the Caller) to represent the invocation +1. Allocate a unique (per connection) `Invocation ID` value (arbitrary string, chosen by the Caller) to represent the invocation 2. Send an `Invocation` or `StreamingInvocation` message containing the `Invocation ID`, the name of the `Target` being invoked, and the `Arguments` to provide to the method. 3. If the `Invocation` is marked as non-blocking (see "Non-Blocking Invocations" below), stop here and immediately yield back to the application. 4. Wait for a `StreamItem` or `Completion` message with a matching `Invocation ID`