Ticket #4403 (closed enhancement: duplicate)

Opened 6 years ago

Last modified 6 years ago

Ability to switch from gabble to salut manually

Reported by: yani Owned by: yani
Priority: high Milestone: Future Release
Component: presence-service Version:
Keywords: Cc: gdesmott, wad, carrano
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

There are reasons for the gabble service not to be enabled always automatically. Some specific configurations require necessary the user to be able to switch manually from gabble to salut.

The user must choose between: 1.auto(current case), 2.gabble, 3.salut

This can be implemented in controlpanel, but a commandline option can be very useful. The switch should be able to be accesed from other activities.

Change History

follow-up: ↓ 3   Changed 6 years ago by smcv

Is this for the benefit of developers, children, both, ...?

Why is this feature needed?

Why do other activities need to be able to control the policy?

In the brave new world of Rainbow, will changing the connectivity be a privileged action that only certain activities can do?

If this is for use by the children, we could do with some idea of what the UI for this will be like and what it'll require. If it's for developers, it'd still be useful to know what the requirements are.

  Changed 6 years ago by jg

  • owner changed from morgs to yani

Yani, why, the assembled masses would like to know?

in reply to: ↑ 1 ; follow-up: ↓ 4   Changed 6 years ago by yani

Replying to smcv:

Is this for the benefit of developers, children, both, ...? Why is this feature needed? Why do other activities need to be able to control the policy? In the brave new world of Rainbow, will changing the connectivity be a privileged action that only certain activities can do? If this is for use by the children, we could do with some idea of what the UI for this will be like and what it'll require. If it's for developers, it'd still be useful to know what the requirements are.

i am quoting an email I sent to kim, that she agreed to:


there are several occasions where an XO with valid internet connectivity might need Salut instead of connecting to a jabber server. 1. When 2 XOs are connected to the same Schoolserver, and the jabber server at some point fails, or becomes very slow for his own reason. Then the XOs must have the choice to share an activity. 2. If an XO is connected to a secure AP that the other XOs are not authorized to connect to. 3. If an XO is connected to an AP that other XO cannot reach directly but only through the mesh, they must be able to communicate. In fact they can if the first XO becomes an MPP. But it might not prefer to because i. MPPs have unreliable ability to share activities(although I have tested it and it works through a jabber server, but it is might not be a general case) ii. an MPP might me loaded with extreme traffic, whereas the XO might only wanna share a simple activity with a single other XO 4. If a schoolserver mesh is very small(3-4 XOs) it is faster to share using salut. This can be very useful when the internet connectivity is unreliable at times.

So to answer your question it is for the benefit of the user(children), but it is very useful for developers too

We require an API to set mode between auto,gabble,salut

The option is not meant to be used by general activities, but specifically by Test activity, the control panel, the neighbour view(or activities controling the neighbor view), the console

in reply to: ↑ 3   Changed 6 years ago by yani

Similar issue it 4463, that regards an API to manually connect/disconnect to a specific jabber server

  Changed 6 years ago by jg

  • milestone changed from Never Assigned to Future Release

  Changed 6 years ago by gdesmott

  • cc gdesmott added

  Changed 6 years ago by gdesmott

IMHO children shouldn't have to care about that. The XO is configured to use the "best" connectivity available.

We could consider adding a option in sugar/default/config (tweakable using the control panel) but I'm not convince that's so useful.

  Changed 6 years ago by yani

  • cc wad, carrano added

the way we do it at the moment is

sugar-control-panel -s jabber foo

so Gabble will fail, and salut will be forced

  Changed 6 years ago by morgs

  • status changed from new to closed
  • next_action set to never set
  • resolution set to duplicate

Superceded by #6594

Note: See TracTickets for help on using tickets.