/usr/share/pyshared/telepathy/_generated/Client_Approver.py is in python-telepathy 0.15.19-2.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 | # -*- coding: utf-8 -*-
# Generated from the Telepathy spec
"""Copyright © 2008-2009 Collabora Ltd.
Copyright © 2008-2009 Nokia Corporation
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
"""
import dbus.service
class ClientApprover(dbus.service.Object):
"""\
Approvers are clients that notify the user that new channels have
been created by a contact, and allow the user to accept or reject
those channels. The new channels are represented by a ChannelDispatchOperation
object, which is passed to the
AddDispatchOperation method.
For instance, Empathy's tray icon, or the answer/reject window
seen when a Maemo device receives a VoIP call, should be
Approvers.
Approvers can also select which channel handler will be used for the
channel, for instance by offering the user a list of possible
handlers rather than just an accept/reject choice.
However, the Channel Dispatcher must be able to prioritize
possible handlers on its own using some reasonable heuristic,
probably based on user configuration.
It is possible (and useful) to have an approver and
a channel handler in the same process; this is particularly useful
if a channel handler wants to claim responsibility for particular
channels itself.
All approvers are notified simultaneously. For instance, in a
desktop system, there might be one approver that displays a
notification-area icon, one that is part of a contact list
window and highlights contacts there, and one that is part
of a full-screen media player.
Any approver can approve the handling of a channel dispatch operation
with a particular channel handler by calling the HandleWith
method. Approvers can also attempt to Claim
channels; if this succeeds, the approver may handle the channels
itself (if it is also a Handler), or close the channels in order to
reject them.
At the D-Bus level, there is no "reject" operation: approvers wishing
to reject channels SHOULD call the Claim method, then (if it succeeds)
close the channels in any way they see fit.
The first approver to reply gets its decision acted on; any other
approvers that reply at approximately the same time will get a D-Bus
error, indicating that the channel has already been dealt with.
Approvers should usually prompt the user and ask for
confirmation, rather than dispatching the channel to a handler
straight away.
"""
@dbus.service.method('org.freedesktop.Telepathy.Client.Approver', in_signature='a(oa{sv})oa{sv}', out_signature='')
def AddDispatchOperation(self, Channels, DispatchOperation, Properties):
"""
Called by the channel dispatcher when a ChannelDispatchOperation
in which the approver has registered an interest is created,
or when the approver starts up while such channel dispatch
operations already exist.
The channel dispatcher SHOULD call this method on all approvers
at the same time. If an approver returns an error from this method,
the approver is assumed to be faulty.
If no approvers return from this method
successfully (including situations where there are no matching
approvers at all), the channel dispatcher SHOULD consider this
to be an error, and recover by dispatching the channel to the
most preferred handler.
Processes that aren't approvers (or don't at least ensure that there
is some approver) probably shouldn't be making connections
anyway, so there should always be at least one approver running.
"""
raise NotImplementedError
|