Use same timestamp as SendingTime in outbound FIX and FixMessage.timestamp #550
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When scanning archive it is useful to have the same local timestamp both in SBE FixMessage and sent FIX. This allows reading high-precision version of SendingTime w/o decoding the header, speeding up date-range queries for sessions like market data feeds which mostly send data.
The change affects session messages and application messages sent using
trySend(Encoder)
overloads. There is new variant oftrySend(DirectBuffer)
which accepts already encoded FIX and timestamp, which is kept as private method for now.