Add queryallactions operation
#1232
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
from today's TD call, the group decided to merge this PR |
takuki
added a commit
to takuki/wot-thing-description
that referenced
this pull request
Jan 30, 2022
egekorkan
pushed a commit
to egekorkan/wot-thing-description
that referenced
this pull request
Feb 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the
queryallactionsoperation proposed in #1200.You may be pleased to know this is probably the final operation I'm going to propose for Thing Description 1.1. There are other potential candidates (like
invokeanyaction,cancelallactions,queryactioninstance,cancelactioninstanceandreadpastevents) but I think we can live without them.I think
queryallactionsis particularly important because without it there may be no way for a Consumer to enumerate ongoing actions, which may mean that only the Consumer which invokes an action can ever query its status and if that Consumer should crash, it may lose the reference to a dynamic resource needed to do so. This operation is probably also needed for the Core Profile, see w3c/wot-profile#99.There's still some discussion about the payload format for meta operations, but this is being discussed in #1231.
Preview | Diff