Opened 10 years ago

Last modified 20 months ago

#3445 new defect

Collaboration initiator can't leave a collaboration session

Reported by: uwog Owned by: uwog
Priority: high Milestone:
Component: write-activity (abiword) Version:
Keywords: relnote Cc: gregorio, sascha_silbe
Blocked By: Blocking:
Deployments affected: Action Needed: never set
Verified: no


Consider an activity being shared by person S, and joined by persons C1, C2, and C3.

Persons C1, C2 and C3 are allowed to leave and rejoin the collaboration session. However the whole session will stop working when person S leaves (because he is controlling the whole session.

AbiCollab requires that one person 'owns' the session, as this is required to do proper collision handling.

We should implement a way to automatically select a new session owner to hand over control to as soon as the current owner leaves the session. This will be a lot more intuitive to the people involved in the session.

Note that this will cause a tiny lag while collaborating (somewhere between 0 and 5 seconds in practice I think), while AbiCollab makes the documents agree to a common state before handing over control.

Change History (8)

comment:1 Changed 10 years ago by jg

  • Milestone changed from Untriaged to First Deployment, V1.0
  • Priority changed from normal to high

This seems quite important.

comment:2 Changed 9 years ago by uwog

  • Action Needed set to never set
  • Summary changed from Activitity owner can't leave a collaboration session to Collaboration initiator can't leave a collaboration session

I've started implement the code support for session takeover in AbiCollab ( It will take a bunch of work to backport to STABLE, and the Tubes backend does not support it (yet).

comment:3 Changed 8 years ago by gregorio

  • Cc gregorio added
  • Keywords relnote added

Hi Guys,

Does this affect all shared activities or just write?

Here is the text I plan to put in the 8.2 release notes for this one:
"If the initiator of a shared activity exits their activity or stops sharing the collaboration ends for all XOs sharing the activity. "

let me know if that is correct or if you have any comments or edits.


Greg S

comment:4 Changed 8 years ago by uwog

Hi Greg,

As far as I know, this is Write specific.

This issue is being worked on, but it takes a lot of really tricky code to write, and I have a day job as well to attend to :)

comment:5 Changed 8 years ago by gregorio

Hi Guys,

Was any progress made on this lately?

Its still an important issue for Uruguay and other deployments.

Let me know if I anyone has suggestions about who can work on it.


Greg S

comment:6 Changed 8 years ago by uwog

The only person who knows the protocol well enough at the moment to finish it is me unfortunately. The only thing holding back the finishing of the issue is time.
I'm trying to get funding from NLnet to finish this, amongst other collaboration issues. Should know more in the coming days.

comment:7 Changed 8 years ago by sascha_silbe

  • Cc sascha_silbe added

comment:8 Changed 20 months ago by Quozl

  • Milestone 8.2.0 (was Update.2) deleted

Milestone 8.2.0 (was Update.2) deleted

Note: See TracTickets for help on using tickets.