Skip to content
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 disconnectHandler to ShadowParameters_t #9

Closed
wants to merge 1 commit into from

Conversation

gthole
Copy link

@gthole gthole commented Dec 18, 2015

Issue: aws_iot_shadow_connect defaults the MQTTClientParameters.disconnectHandler to NULL with no way to override through the ShadowParameters_t pParams argument. Cases where aws_iot_shadow_connect is used to connect the MQTT Client should be able to specify a disconnect handler.

This PR adds disconnectHandler to ShadowParameters_t with a NULL default value for ShadowParametersDefault so no change is required to sample apps or existing implementations. This same approach could be applied to other parameters in MQTTConnectParams as well, if needed.

Alternately, we could change ShadowParameters_t to take MQTTConnectParams directly to avoid this overlap, but that would be a breaking change.

@johnrotach
Copy link

Hello Greg,

Thanks much for submitting this! From the initial look the change makes a lot of sense. Our normal procedure is to pull PR code into our internal repo and run it through our development process and then release it. When we target a release for this we'll comment back and close this PR.

John
AWS IoT

@gthole
Copy link
Author

gthole commented Dec 21, 2015

Sounds great! Thanks John.

@gthole
Copy link
Author

gthole commented Apr 26, 2016

Any progress on this? There has been a release since I originally posted this, and it's still an issue in the current SDK. Thanks!

@chaurah
Copy link
Contributor

chaurah commented Jun 12, 2016

Hi @gthole,
The disconnect handler has been added to ShadowInitParams in v2.0.0 of the SDK. Please accept my apologies for the delayed response to this issue. I should have closed this when the new version of the SDK was released.

Rahul

@chaurah chaurah closed this Jun 12, 2016
@J-Millett J-Millett mentioned this pull request Jul 30, 2019
aggarw13 added a commit to aggarw13/aws-iot-device-sdk-embedded-C that referenced this pull request Nov 29, 2019
Add infrastructure for running CI-based integration tests, and add demo application
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants