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

should the q field be changed when sending buffered messages? #73

Closed
Tracked by #78
, #36
...
emiltin opened this issue Aug 5, 2021 · 2 comments
Closed
Tracked by #78
, #36
...

should the q field be changed when sending buffered messages? #73

emiltin opened this issue Aug 5, 2021 · 2 comments
Labels
clarify
Milestone
3.2

Comments

@emiltin
Copy link
Contributor

emiltin commented Aug 5, 2021

No description provided.

@emiltin emiltin added the clarify label Sep 7, 2021
@emiltin emiltin added this to the 3.2 milestone Sep 16, 2021
otterdahl added a commit that referenced this issue Oct 25, 2021
@otterdahl
Clarify that the q field should changed during buffering
1030a13 
The "q" field in status messages should be set to "old" when sending buffered
messages.

Fixes #73
@otterdahl
Copy link
Contributor

Yes. It should. I suggest we add the following

Communication disruption

  • When sending buffered status messages, the q field should be set to old

Return values (returnvalue)

Element Value Description
q old The value is not up to date. Used when sending buffered values

Added in 1030a13

@otterdahl otterdahl mentioned this issue Oct 25, 2021
Merged
18 tasks
@emiltin
Copy link
Contributor Author

emiltin commented Oct 29, 2021

done

@emiltin emiltin closed this as completed Oct 29, 2021
@otterdahl otterdahl mentioned this issue May 22, 2023
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
clarify
Projects
None yet
Milestone
3.2
Development

No branches or pull requests
2 participants
@emiltin @otterdahl