From 6d89f5fa66d544ea6b41e93853c23292505e49c6 Mon Sep 17 00:00:00 2001 From: Hanno Klein Date: Thu, 15 Apr 2021 18:47:46 +0200 Subject: [PATCH] Final typo corrections --- .../doc/04PointToPointSessionProtocol.md | 2 +- v1-0-STANDARD/doc/07UsageExamples.md | 102 +++++++++--------- .../FIX_Performance_Session_Layer_V1.0.docx | Bin 0 -> 504048 bytes .../FIX_Performance_Session_Layer_V1.0.pdf | Bin 0 -> 1397954 bytes 4 files changed, 52 insertions(+), 52 deletions(-) create mode 100644 v1-0-STANDARD/doc/publication/FIX_Performance_Session_Layer_V1.0.docx create mode 100644 v1-0-STANDARD/doc/publication/FIX_Performance_Session_Layer_V1.0.pdf diff --git a/v1-0-STANDARD/doc/04PointToPointSessionProtocol.md b/v1-0-STANDARD/doc/04PointToPointSessionProtocol.md index c372aa2..53eabba 100644 --- a/v1-0-STANDARD/doc/04PointToPointSessionProtocol.md +++ b/v1-0-STANDARD/doc/04PointToPointSessionProtocol.md @@ -387,7 +387,7 @@ The recoverable server return flow should report the result of operations at the ### Applied -This is an optional application response message to support an idempotent flow. Standard FIX semantics provide application layer acknowledgements to requests, e.g. Execution Report in response to New Order Single. The principle is to use application specific acknowledgement messages where possible; use the Applied message where an application level acknowledgement message does not exist. +This is an optional application response message to support an idempotent flow. Standard FIX semantics provide application layer acknowledgements to requests, e.g. ExecutionReport in response to NewOrderSingle. The principle is to use application specific acknowledgement messages where possible; use the Applied message where an application level acknowledgement message does not exist. Since Applied is an application message, it will be reliably delivered if returned on a recoverable flow. diff --git a/v1-0-STANDARD/doc/07UsageExamples.md b/v1-0-STANDARD/doc/07UsageExamples.md index 2e7b868..390ba63 100644 --- a/v1-0-STANDARD/doc/07UsageExamples.md +++ b/v1-0-STANDARD/doc/07UsageExamples.md @@ -1,4 +1,4 @@ -# Appendix A - Usage Examples (TCP) +EstablishmentReject # Appendix A - Usage Examples (TCP) These use cases contain sample values for illustrative purposes only @@ -128,7 +128,7 @@ For example – the Negotiate message is neither accepted nor rejected and one K | Negotiate |   | ABC | T1 | -- | Unsequenced | -- | -- | -- | | | NegotiationResponse | ABC | -- | T1 | -- | -- | -- | Unsequenced | | Establish | | ABC | T2 | -- | -- | 10 | -- | -- | -| | Establish mentAck | ABC | -- | T2 | -- | 10 | -- | -- | +| | EstablishmentAck | ABC | -- | T2 | -- | 10 | -- | -- | ### Establishment (idempotent) @@ -137,7 +137,7 @@ For example – the Negotiate message is neither accepted nor rejected and one K | Negotiate |   | ABC | T1 | -- | Idempotent | -- | -- | -- | | | NegotiationResponse | ABC | -- | T1 | -- | -- | -- | Recoverable | | Establish | | ABC | T2 | -- | -- | 10 | 1 | -- | -| | Establish mentAck | ABC | -- | T2 | -- | 10 | 1 | -- | +| | EstablishmentAck | ABC | -- | T2 | -- | 10 | 1 | -- | ### Establishment (none) @@ -146,7 +146,7 @@ For example – the Negotiate message is neither accepted nor rejected and one K | Negotiate |   | ABC | T1 | -- | None | -- | -- | -- | | | NegotiationResponse | ABC | -- | T1 | -- | -- | -- | None | | Establish | | ABC | T2 | -- | -- | 10 | -- | -- | -| | Establish mentAck | ABC | -- | T2 | -- | 10 | -- | -- | +| | EstablishmentAck | ABC | -- | T2 | -- | 10 | -- | -- | ### Establishment rejects @@ -157,7 +157,7 @@ For example – Trying to send an Establish message without first Negotiating th | **Message Received** | **Message Sent** | **Session ID** | **Timestamp** | **Request Timestamp** | **Code** | **Reason** | **Keep Alive Interval** | |----------------------|-----------------------|----------------|---------------|-----------------------|--------------|-----------------------------------------------|-------------------------| | Establish | | ABC | T2 | -- | -- | -- | 10 | -| | Establish ment Reject | ABC | -- | T2 | Unnegotiated | Establishment Not Allowed Without Negotiation | -- | +| | EstablishmentReject | ABC | -- | T2 | Unnegotiated | Establishment Not Allowed Without Negotiation | -- | #### Already established @@ -166,11 +166,11 @@ For example – Trying to send an Establish message when the session itself is a | **Message Received** | **Message Sent** | **Session ID** | **Timestamp** | **Request Timestamp** | **Code** | **Reason** | **Keep Alive Interval** | |----------------------|----------------------|----------------|---------------|-----------------------|---------------------|--------------------------------|-------------------------| | Negotiate |   | ABC | T1 | -- | -- | -- | -- | -| | Negotiation Response | ABC | -- | T1 | -- | -- | -- | +| | NegotiationResponse | ABC | -- | T1 | -- | -- | -- | | Establish | | ABC | T2 | -- | -- | -- | 10 | -| | Establish mentAck | ABC | -- | T2 | -- | -- | 10 | +| | EstablishmentAck | ABC | -- | T2 | -- | -- | 10 | | Establish | | ABC | T3 | -- | -- | -- | 10 | -| | Establish mentReject | ABC | -- | T3 | Already Established | Session is Already Established | -- | +| | EstablishmentReject | ABC | -- | T3 | Already Established | Session is Already Established | -- | #### Session blocked @@ -201,9 +201,9 @@ For example – Session ID does not follow UUID or GUID semantics as per RFC 412 | **Message Received** | **Message Sent** | **Session ID** | **Timestamp** | **Request Timestamp** | **Code** | **Reason** | **Keep Alive Interval** | |----------------------|----------------------|----------------|---------------|-----------------------|-------------|---------------------------|-------------------------| | Negotiate |   | ABC | T1 | -- | -- | -- | -- | -| | Negotiation Response | ABC | -- | T1 | -- | -- | -- | +| | NegotiationResponse | ABC | -- | T1 | -- | -- | -- | | Establish | | 000 | T2 | -- | -- | -- | 10 | -| | Establish mentReject | 000 | -- | T2 | Unspecified | Invalid Session ID Format | 10 | +| | EstablishmentReject | 000 | -- | T2 | Unspecified | Invalid Session ID Format | 10 | #### Invalid request timestamp @@ -212,9 +212,9 @@ For example – Timestamp follows Unix Epoch semantics and is to be sent with na | **Message Received** | **Message Sent** | **Session ID** | **Timestamp** | **Request Timestamp** | **Code** | **Reason** | **Keep Alive Interval** | |----------------------|----------------------|----------------|---------------|-----------------------|-------------|--------------------------|-------------------------| | Negotiate |   | ABC | T1 | -- | -- | -- | -- | -| | Negotiation Response | ABC | -- | T1 | -- | -- | -- | +| | NegotiationResponse | ABC | -- | T1 | -- | -- | -- | | Establish | | ABC | 86400 | -- | -- | -- | 10 | -| | Establish mentReject | ABC | -- | 86400 | Unspecified | Invalid Timestamp Format | 10 | +| | EstablishmentReject | ABC | -- | 86400 | Unspecified | Invalid Timestamp Format | 10 | #### Bad credentials @@ -266,11 +266,11 @@ When the KeepAliveInterval has expired and no keep alive message is received the | Negotiate |   | ABC | T1 | -- | Idempotent | -- | -- | -- | | | NegotiationResponse | ABC | -- | T1 | -- | -- | -- | -- | | Establish | | ABC | T2 | -- | -- | 10 | -- | -- | -| | Establish mentAck | ABC | -- | T2 | -- | 10 | -- | -- | +| | EstablishmentAck | ABC | -- | T2 | -- | 10 | -- | -- | | \