+static void
+on_connection_status_changed (TnyAccount *account, TnyConnectionStatus status, gpointer user_data)
+{
+ printf ("DEBUG: %s: status=%d\n", __FUNCTION__, status);
+
+ if (status == TNY_CONNECTION_STATUS_DISCONNECTED) {
+ /* A tinymail network operation failed, and tinymail then noticed that
+ * the account is offline, because our TnyDevice is offline,
+ * because libconic says we are offline.
+ * So ask the user to go online again.
+ *
+ * Note that this signal will not be emitted if the account was offline
+ * when the network operation was first attempted. For those cases,
+ * the application must do its own explicit checks.
+ *
+ * We make sure that this UI is shown in the main thread, to avoid races,
+ * because tinymail does not guarantee that this signal handler will be called
+ * in the main thread.
+ */
+ /* TODO: Commented out, because this causes hangs, probably related to
+ * our use of mainloops:
+ * modest_platform_connect_and_wait (NULL);
+ */
+ } else if (status == TNY_CONNECTION_STATUS_CONNECTED_BROKEN) {
+ printf ("DEBUG: %s: Connection broken. Forcing TnyDevice offline.\n",
+ __FUNCTION__);
+
+ /* Something went wrong during some network operation.
+ * Stop trying to use the network now,
+ * by forcing accounts into offline mode:
+ *
+ * When libconic reconnects, it will set the device back online again,
+ * regardless of it being forced offline before.
+ */
+ /* TODO: Find out when this is falsely being emitted. */
+ printf (" DEBUG: %s: Not forcing offline because tinymail is sometimes reporting false connection breaks.\n",
+ __FUNCTION__);
+ /*
+ TnyDevice *device = modest_runtime_get_device ();
+ tny_device_force_offline (device);
+ */
+ }
+}
+