[Telepathy] On spec additions to allow a really simple IM API
ollisal at gmail.com
Tue Mar 8 00:39:10 PST 2011
On Mon, Mar 7, 2011 at 5:24 PM, <mikhail.zabaluev at nokia.com> wrote:
>> -----Original Message-----
>> From: telepathy-
>> bounces+mikhail.zabaluev=nokia.com at lists.freedesktop.org
>> bounces+mikhail.zabaluev=nokia.com at lists.freedesktop.org] On Behalf Of
>> ext Will Thompson
>> Sent: Monday, March 07, 2011 4:49 PM
>> To: Zabaluev Mikhail (Nokia-MS/Helsinki)
>> Cc: telepathy at lists.freedesktop.org
>> Subject: Re: [Telepathy] On spec additions to allow a really simple IM
>> On 07/03/11 14:45, mikhail.zabaluev at nokia.com wrote:
>> > Anyone for o.fd.Tp.Conn.I.MessageSender, with suitable hacks to avoid
>> invoking approvers/handlers for a possibly created channel?
>> The main reason I wanted to use channels for this, rather than a
>> connection interface, is that otherwise observers will not notice the
>> messages being sent. A connection interface is simpler but we have to
>> figure out how these messages should get logged etc.
> Yes, so there should be a way to get the created channel to be observed, but not offered to approvers and/or handlers? May just setting Channel.Requested to true be enough?
The system text chat UI as a Handler wants both Requested = true and
Requested = false channels. For Text this means locally initiated text
chats, and chats initiated by a remote contact sending us a message.
That said, we could of course define some non-overloaded D-Bus
property for indicating that "this is a Channel which only observers
should accept, and others should include a = false match for it in
their filters". This would require adding such a "ignore" rule to all
approver and client filters though, which seems unclean - or hacking
handling for it into the Channel Dispatcher.
Also, as this Connection API would spawn a Channel for observation
purposes, who closes it? A simple answer would be "the CM, if the
channel hasn't been requested again" (similarly to our earlier
proposal for doing this in the CD - however, the CM is in an even
better position to do just that!) but what if the Observer Claims the
Channel? There is no way in current Telepathy for the CM to get an
indication that the Channel was Claimed - whereas the CD would know
this (but is riddled with other problems implementing this, see Will's
reply). Well, we could then possibly say that an Observer can't Claim
channels which have the ObserversOnly property set to true... this is
rapidly making the channel dispatching and behavior rules for Clients
Unfortunately, it seems that any solution for this issue is riddled
with special-case rules and inconsistencies.
> Best regards,
> telepathy mailing list
> telepathy at lists.freedesktop.org
More information about the telepathy