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

Clarify timestamp behavior in protocol documentation #219

Merged
merged 1 commit into from
Nov 14, 2024
Merged

Clarify timestamp behavior in protocol documentation #219

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion textile/protocol.textile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,7 @@ The members are as follows.
Client libraries do not need to populate this field if the clientId is implicit (ie a clientId was specified when the library was initialized, and is therefore connection-wide. Also, this field will be empty if no clientId has been specified either on library initialization or when publishing the message.<br><br>
Messages sent from the service to the client will contain a clientId if one is available.

- i64 timestamp := This is the timestamp indicating the time at which the message was received by the system from the publishing client. The timestamp is included in messages sent by the service to the client. The field is expected to be empty in messages sent from a client to the service.
- i64 timestamp := This is the timestamp indicating the time at which the message was first received by the system from a publishing client. Subsequent updates to this message shall not update the timestamp. The timestamp is included in messages sent by the service to the client. The field is expected to be empty in messages sent from a client to the service.

- string or binary data := The payload of the message, binary is supported when using MessagePack.

Expand Down
Loading