Page History
...
| Note |
|---|
| Venues may reject multiple identical requests, so care should be taken to ensure that there is a clear demarcation of responsibility across Users. |
| Note |
|---|
Only the last user to logout from a venue will cause Whisperer to logout from the Venue. It follows then that when multiple users are configured, when logging off prior users, it is the responsibility of the MFSBE4 client to ensure that the user session is cleaned up correctly prior to logout. |
Venue as Taker
A single User must be defined, to avoid the need for configuration and logic to be maintained within MarketFactory to route each Venue QuoteRequest to specific individual Users.
...
| 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 | ||
|---|---|---|
| ||
Illustrate Multiplexing - if we have multuiple multiple users connecting to single venue, and first Venue. 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 |
...
Overview
Content Tools