Bug 25991

Summary:	Conference spec shouldn't require only using either of InitialIds or InitialChannels
Product:	Telepathy	Reporter:	Sjoerd Simons <sjoerd>
Component:	tp-spec	Assignee:	Simon McVittie <smcv>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	danielle
Version:	0.8	Keywords:	patch
Hardware:	Other
OS:	All
URL:	http://git.collabora.co.uk/?p=user/smcv/telepathy-spec-smcv.git;a=shortlog;h=refs/heads/conf-initial-union
Whiteboard:	review+
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	24906

Description Sjoerd Simons 2010-01-11 07:15:33 UTC

Use-case:
  I've got a 1-to-1 chat in a channel and i want to invite a@b in it so i request a new one with   InitialChannels = [ MyChannel] , InitialIds = [ "a@b" ]

The new channel should then be a continuation only of MyChannel and not of any channel you may already have open with a@b.


Also smcv mentiones that it might make sense to have InitialIds on the new channel be the union of the requested InitialIds and the TargetIds of the channels in InitialChannels.

Comment 1 Danielle Madeley 2010-01-13 02:38:14 UTC

(In reply to comment #0)

> Also smcv mentiones that it might make sense to have InitialIds on the new
> channel be the union of the requested InitialIds and the TargetIds of the
> channels in InitialChannels.

That's how it's implemented in Gabble atm. InitialInviteeIDs and InitialInviteeHandles is the union of Initial*.

Comment 2 Simon McVittie 2010-03-02 05:02:28 UTC

Does the branch smcv/conf-initial-union make this clearer?

Comment 3 Simon McVittie 2010-03-11 07:56:40 UTC

r+ from wjt

Comment 4 Simon McVittie 2010-03-11 09:42:48 UTC

Fixed in git for 0.19.2

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.