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 2: the MQTT Android service to reconnect to the MQTT server after network connectivity is reestablished) |
(→Requirement 1: offline inbound buffering) |
||
| Line 2: | Line 2: | ||
=== Design (no implementation code please - only external design and application code!) == | === Design (no implementation code please - only external design and application code!) == | ||
| − | ==== Requirement 1: | + | ==== Requirement 1: Buffering of inbound messages when app is not running ==== |
The MQTT Android service to receive messages while the app is not running. | The MQTT Android service to receive messages while the app is not running. | ||
Revision as of 07:50, 26 September 2014
Contents
= Design (no implementation code please - only external design and application code!)
Requirement 1: Buffering of inbound messages when app is not running
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?