-
Notifications
You must be signed in to change notification settings - Fork 38
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.
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
Add macros to API for compile time topic generation #38
Add macros to API for compile time topic generation #38
Conversation
…mpile-time-job-generation
source/include/jobs.h
Outdated
@@ -192,6 +292,13 @@ typedef enum | |||
* | |||
* @note The thingName parameter does not need a NUL terminator. | |||
* | |||
* @note The AWS IoT Jobs service does not require clients to subscribe | |||
* to the "/accepted" and "/rejected" response topics for the APIs that | |||
* accept PUBLISH requests. The Jobs service will send responses to requests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could change wording here, "publish requests" sounds like a request for a publish instead of a request delivered via publish
* accept PUBLISH requests. The Jobs service will send responses to requests | |
* accept published requests. The Jobs service will send responses to requests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reworded to address the readability concern.
* This macro should be used when the thing name and jobID are known at the | ||
* compile time. If next pending job is being queried, use $next as job ID. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is job ID ever known at compile time?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This macro's main utility would be for using the $next
job ID. If you think that we should provide macros only for that case, I can limit the macro to generate topics only for the next job ID.
This PR makes the following changes:
Add macros to API to allow generation of topics at compile time if thing name and job ID (for topics that need job ID) are known to application at compile time.
Add documentation to function APIs about the AWS IoT Jobs service not needing subsciption to response topics of DescribeJobExecution, UpdateJobExecution, GetPendingJobExecutions and StartNextPendingJobExecution APIs