Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Paho/Android Service"
< Paho
(→Requirement 1: the MQTT Android service to receive messages while the app is not running) |
(→Requirement 2: the MQTT Android service to reconnect to the MQTT server after network connectivity is reestablished) |
||
| Line 8: | Line 8: | ||
Questions: when are these messages delivered to the application? How does the app reestablish its connection to the service to get the same messages? | Questions: when are these messages delivered to the application? How does the app reestablish its connection to the service to get the same messages? | ||
| − | ==== Requirement 2: | + | ==== Requirement 2: automatic reconnection ==== |
| + | |||
| + | The application does not have to reconnect itself. | ||
Using Android notifications to recognize when the network is available again. | Using Android notifications to recognize when the network is available again. | ||
Revision as of 07:49, 26 September 2014
Contents
= Design (no implementation code please - only external design and application code!)
Requirement 1: offline inbound buffering
The MQTT Android service to receive messages while the app is not running.
Questions: when are these messages delivered to the application? How does the app reestablish its connection to the service to get the same messages?
Requirement 2: automatic reconnection
The application does not have to reconnect itself.
Using Android notifications to recognize when the network is available again.
Automatic reconnect can be configured, and turned off.
Requirement 3: automatic service reconnect after network failure
== Requirement 4:
What is the application/service lifecycle?