Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ResourceIdentifier - HTTP command & control
See original GitHub issueIs there any reason, why the resource path for command & control responses doesn’t match the ResourceIdentifier?
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Identifying resources on the Web - HTTP - MDN Web Docs
Each resource is identified by a Uniform Resource Identifier (URI) used throughout HTTP for identifying resources.
Read more >Identifying resources - Cloud Control API - AWS Documentation
When using Cloud Control API commands, you can specify the primary identifier or any secondary identifier defined for the resource type in its...
Read more >What is a Uniform Resource Identifier (URI)? - TechTarget
A URI is a character sequence that helps identify a logical or physical resource connected to the internet. Read more about key elements, ......
Read more >Universal Resource identifiers in WWW
A Universal Resource Identifier (URI) is a member of this universal set of names in ... The search part, if present, is sent...
Read more >Universal Resource Identifier patterns - IBM
Universal Resource Identifier patterns. Each REST API resource can be accessed by using a Uniform Resource Identifier (URI).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FMPOV there is no need to repeat the mistake that we made with the HTTP adapter when we put the
resinto the the resource path for sending a command response. For the CoAP adapter we could as well use something likecommand_response/$TENANT/$DEVICE_ID/$REQUEST_ID[?$QUERY_PARAMS]That would allow us to use
ResourceIdentifieras-is, wouldn’t it?WDYT @boaks @calohmn ?
The PR is adapted.