...
This seems to be the same as 1?
Session Handling
Logon
Standard Scenarios
| Gliffy Diagram |
|---|
| name | Logon 4.0 Sequence_3 |
|---|
| pagePin | 3 |
|---|
|
Logon After Session Establishment
| Gliffy Diagram |
|---|
| name | 4.0 Schema_2ndLogon |
|---|
| pagePin | 7 |
|---|
|
Heartbeats
| Gliffy Diagram |
|---|
| name | 4.0 Schema_Heartbeat_3 |
|---|
| pagePin | 2 |
|---|
|
| Note |
|---|
|
User fails to respond to a testrequest and sends no messages Same but in the opposite direction. |
Logout
| Note |
|---|
|
Client FH logout. User sends initiates a transaction after either sending/ receiving a logout. |
MarketDefinition and SecurityDefinition
| Gliffy Diagram |
|---|
| name | 4.0 MarketDefinition_SecurityDefinition.05 |
|---|
| pagePin | 1 |
|---|
|
Venue Login
| Note |
|---|
|
Illustrate multiple logon attempts to venue - 5 attempts, one minute interval, then logout to client. Eg Consider Reuters MAPI. |
| Note |
|---|
|
Illustrate what happens when Venue or Client connection is dropped. |
| Note |
|---|
|
Illustrate EOD session/seq num resets. |
| Note |
|---|
|
Multiplexing - if we have multuiple users connecting to single venue, and first user triggers logon, last user triggers logout, how de we support first user logout cleanly - eg their order cancellations that they need to be notified of... |
| Note |
|---|
|
user sends initiates a transaction after after receiving a loggedout user notification |
| Gliffy Diagram |
|---|
| name | 4.0 Schema_Heartbeat.03 |
|---|
| pagePin | 2 |
|---|
|
Previously Quoted
ESP/RFS Order State Transition Diagram
...