huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Specify invocation ids are unique per connection (#4316) 

Make it clear that invocation ids are unique per connection
This commit is contained in:
David Fowler 2018-11-29 10:13:09 -08:00 committed by GitHub
parent 26dfce1f3c
commit 1b46549ec4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/SignalR/specs/HubProtocol.md
View File

@ -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`