We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From the changelog:
If an object is not known during status request or command request, the site must not disconnect but instead reply with "ageState" set to "undefined"
There is nothing called ageState in the spec. Does it refer to the q attribute of StatusResponse messages?
The text was updated successfully, but these errors were encountered:
Changelog for Version 1.1n (2011-11-02) mentions:
"unknown" added as a possible ageState
So it seems the value has beeen there for a long time, it's behaviour that changed in 3.1.3. ie don't disconnect?
Sorry, something went wrong.
"ageState" changed to "q" (quality) when switching from XML to JSON (See RSMP 3.1.3, page 34). This is an error of the changelog.
Ok. I suggest fixing this in the changelog.
ChangeLog: Fix name of "ageState" to "q" in changes for RSMP 3.1.3
25d68d3
Fixes #69
5e2bad4
Successfully merging a pull request may close this issue.
From the changelog:
If an object is not known during status request or command request, the site must not disconnect but instead reply with "ageState" set to "undefined"
There is nothing called ageState in the spec. Does it refer to the q attribute of StatusResponse messages?
The text was updated successfully, but these errors were encountered: