Skip to content

Use same timestamp as SendingTime in outbound FIX and FixMessage.timestamp #550

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AndreyNudko
Copy link
Contributor

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 of trySend(DirectBuffer) which accepts already encoded FIX and timestamp, which is kept as private method for now.

@AndreyNudko AndreyNudko force-pushed the master branch 2 times, most recently from d8a8d0d to 0f4ef41 Compare June 6, 2025 09:37
…stamp

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 of `trySend(DirectBuffer)` which accepts already encoded FIX and timestamp, which is kept as private method for now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant