Page History
| Table of Contents |
|---|
Logon
Standard Scenarios
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Logon After Session Establishment
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Heartbeats
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
| 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 | ||||
|---|---|---|---|---|
|
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 | ||||
|---|---|---|---|---|
|
Overview
Content Tools