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
Implementation of a separate resource on the API which would return data about the current state of PBRcontrol should be implemented.
Possible response codes: <200> -> indicates that the API can respond to other requests <404> -> indicates that the API is not running
<200>
<404>
Could be later used for reaching for data about active nodes - this feature must be delayed until Issue #6 is resolved.
The text was updated successfully, but these errors were encountered:
work done on #12
6511412
Information about the ping method can be found here
TODO:
Sorry, something went wrong.
Random id generator implemented, ping now returns the device ids as well
9e100dd
Relevant to issue #12 and Fixes #13
information about the JVM state added to ping response under "jvm", r…
81d3a9a
…elated to #12
No branches or pull requests
Implementation of a separate resource on the API which would return data about the current state of PBRcontrol should be implemented.
Possible response codes:
<200>
-> indicates that the API can respond to other requests<404>
-> indicates that the API is not runningCould be later used for reaching for data about active nodes - this feature must be delayed until Issue #6 is resolved.
The text was updated successfully, but these errors were encountered: