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

Improved performance by instantiating and connecting to MQTT client… #34

Merged
merged 1 commit into from
Jun 28, 2018
Merged

Improved performance by instantiating and connecting to MQTT client… #34

merged 1 commit into from
Jun 28, 2018

Conversation

MarioBajr
Copy link
Contributor

Currently all subscriptionInfo provided by a subscription call instantiates and connects a MQTT client, even if it has no interested topic. And the opposite happens on unsubscribe call, not removing and cleaning unnecessary MQTT clients.

Description of changes:

  • Only instantiate and initialise a new MQTTClient if there is any topic that the AppSyncMQTTClient is interested at.
  • On every unsubscribe call, verify if there is any MQTTClient without interested topic. Disconnecting and removing it.

…s only if it has any interested topic

- Improved performance by disconnecting and removing MQTT clients that has no interested topic
@rohandubal rohandubal merged commit aefe201 into awslabs:master Jun 28, 2018
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.

2 participants