Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Expose EventSequence in client API #261

Open
ibrodkin opened this issue Feb 5, 2025 · 0 comments
Open

Expose EventSequence in client API #261

ibrodkin opened this issue Feb 5, 2025 · 0 comments
Assignees
@ibrodkin
Labels
ChronoLogClient
Milestone
2025-02-28

Comments

@ibrodkin
Copy link
Collaborator

ibrodkin commented Feb 5, 2025

Expose EventSequence in client_chronolog.h

ClientID that is part of the EventSequence should be retained in the form meaningful to the client at the data retrieval point. Make it chrono::service_endpoint value that is also 64bit togetherExpose EventSequence
@ibrodkin ibrodkin added this to the 2025-02-28 milestone Feb 5, 2025
@ibrodkin ibrodkin self-assigned this Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ibrodkin ibrodkin

Labels
ChronoLogClient
Projects
None yet
Milestone
2025-02-28
Development

No branches or pull requests
1 participant
@ibrodkin