http://bugs.freedesktop.org/show_bug.cgi?id=13422
Simon McVittie <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|[email protected].|telepathy- |org |[email protected] Status|ASSIGNED |NEW Summary|Add |Add nice API for channel |tp_connection_create_channel|creation |() and | |tp_connection_ensure_channel| |() | --- Comment #4 from Simon McVittie <[email protected]> 2009-09-29 04:02:15 PST --- We should follow telepathy-qt4's lead on this, since I already designed this feature once :-) I'm no longer sure that we want high-level API for channel creation on the Connection, since the Right Way™ is now to use the ChannelDispatcher. As medium-level API, we should have methods similar to the proposed ones (with an a{sv} parameter), but on the TpAccount (as an implementation detail, they'll talk to the channel dispatcher). As high-level API, in telepathy-qt4 we have API on the Tp::Account like this: PendingOperation *ensureTextChat(QString contact_id, ...); PendingOperation *ensureTextChat(Tp::Contact contact, ...); and similar for ensureMediaCall, ensureTextChatroom, etc. As we gain higher-level API for more channel types, we'll also have createFileTransfer, createContactSearch and so on. We'll only wrap the mode (create/ensure) that is more useful for a particular channel type - for calls and chats you almost always want to ensure, for file transfers and contact searches you always want to create. There is more prior art in libmcclient. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
