[Bug 23151] Chan.I. Room — properties of chatrooms and chatroom-like constructs

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=23151

Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Rethink API for named       |Chan.I.Room — properties of
                   |chatrooms                   |chatrooms and chatroom-like
                   |                            |constructs
                URL|http://git.collabora.co.uk/ |
                   |?p=user/jonny/telepathy-spe |
                   |c.git;a=shortlog;h=refs/hea |
                   |ds/room                     |
             Status|ASSIGNED                    |NEW
  Status Whiteboard|review+ as draft, minor     |draft 1 in 0.19.11
                   |changes                     |
           Keywords|patch                       |
         AssignedTo|jonny.lamb at collabora.co.uk  |telepathy-bugs at lists.freede
                   |                            |sktop.org

--- Comment #18 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-11-08 07:15:59 PST ---
This was merged, so there is no branch.

(In reply to comment #15)
> There could be other types of channels with ad-hoc participation and opaque
> IDs, like calls. All Skype calls have unique IDs. Deemphasize the chat affinity
> of this interface, as it does not seem to be bound to anything specific to text
> channels?

It's called Room and not specific to Text channels, so I think that's OK. When
we say "Room" I think it's OK to mean "identifiable thing you can participate
in". On XMPP, Muji calls take place in a chatroom (which also has a text
component).

It'd be slightly astonishing to use Handle_Type_Room for Skype calls, but they
could work just like Skype group chats as described in the introductory
docstring (Handle_Type_None, TargetID = the opaque ID, this interface, empty
RoomID to indicate that the TargetID is not human-readable).

I'm unsure about Chan.I.Identifier - surely TargetID is the identifier, and the
things that you propose to move to Chan.I.Identifier are extras to aid in
interpretation/display, making the name rather strange?

Over on Bug #26866 there's discussion of whether Chan.I.Addressing should
implicitly only be for contacts. I think it probably should, and we could add a
RoomURI property on this interface if we want to be able to reference (XMPP and
IRC) rooms by URI.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.