Is your feature request related to a problem? Please describe.
We would like to have some improvements in the AppSync SDK for Android, the purpose being to reduce the data usage in the IoT devices.
We are currently using the Android SDK https://github.com/awslabs/aws-mobile-appsync-sdk-android/releases , the last version.
In the SDK, we are using AppSync with some mutations so we can sync some data between the devices and the cloud.
Although, to keep the connection live , the SDK is automatically exchanging some data with the cloud every 15 seconds.
We would like to have in the SDK, the ability to decide the frequency of that exchange, a kind of parameter "keep alive" we can set ourselves, similar to what we have with the aws mqtt sdk.
Describe the solution you'd like
Give Access to the parameter "keep-alive" so the developer can decide for himself, the frequency.
Describe alternatives you've considered
aws mqtt give access; but i want appsync for different project
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
We would like to have some improvements in the AppSync SDK for Android, the purpose being to reduce the data usage in the IoT devices. We are currently using the Android SDK https://github.com/awslabs/aws-mobile-appsync-sdk-android/releases , the last version. In the SDK, we are using AppSync with some mutations so we can sync some data between the devices and the cloud. Although, to keep the connection live , the SDK is automatically exchanging some data with the cloud every 15 seconds. We would like to have in the SDK, the ability to decide the frequency of that exchange, a kind of parameter "keep alive" we can set ourselves, similar to what we have with the aws mqtt sdk.
Describe the solution you'd like Give Access to the parameter "keep-alive" so the developer can decide for himself, the frequency.
Describe alternatives you've considered aws mqtt give access; but i want appsync for different project
Additional context Add any other context or screenshots about the feature request here.