Ticket #5620 (new enhancement)

Opened 7 years ago

Last modified 6 years ago

how should activities handle lost network connections?

Reported by: erikb Owned by: morgs
Priority: normal Milestone: 9.1.0-cancelled
Component: telepathy-other Version:
Keywords: Cc: eben, olpc-dev@…, Collabora, andresambrois
Action Needed: design Verified: no
Deployments affected: Blocked By:
Blocking:

Description

If a network connection is lost, there is no straightforward way for an activity to be alerted and to attempt to reconnect.

If the connection is lost, it is unclear how an activity should attempt to reconnect.

From a ui pov, the shared combobox remains insensitive throughout. Perhaps a notification could go there about the tube connection status?

Change History

Changed 7 years ago by jg

  • milestone changed from Never Assigned to Update.2

Changed 6 years ago by morgs

  • cc Collabora added

See also #4404

Changed 6 years ago by morgs

See also #4158 (notification of mesh dropping)

Changed 6 years ago by morgs

  • next_action set to design

Changed 6 years ago by morgs

  • milestone changed from 8.2.0 (was Update.2) to 9.1.0

Changed 6 years ago by mstone

I met briefly with Steven Murdoch (sjm217) who casually suggested that I begin thinking about designing an API for networking stack clients to query information about the security properties of their communications channels. That information seems somewhat related to information about the capacity, jitter, and latency of the channel. Anyway, I haven't committed to the task yet, but I'll update this ticket if anything comes of it. :)

Changed 6 years ago by andresambrois

  • cc andresambrois added
Note: See TracTickets for help on using tickets.