| Server IP : 182.53.201.61 / Your IP : 216.73.217.175 Web Server : Apache/2.2.15 (Fedora) System : Linux km10.dyndns.org 2.6.31.5-127.fc12.i686.PAE #1 SMP Sat Nov 7 21:25:57 EST 2009 i686 User : apache ( 48) PHP Version : 5.3.3 Disable Function : NONE MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/lib/python2.6/site-packages/telepathy/_generated/ |
Upload File : |
L7Jc @ s2 d Z d d k Z d e i i f d YZ d S( s4 Copyright (C) 2005-2008 Collabora Limited
Copyright (C) 2005-2008 Nokia Corporation
Copyright (C) 2006 INdT
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.
iNt ConnectionManagerc B s e Z d Z e i i d d d d d d Z e i i d d d d d d Z e i i d d d
d d d Z e i i d d
d d Z
RS( s A D-Bus service which allows connections to be created. The manager
processes are intended to be started by D-Bus service activation.
For service discovery, each Telepathy connection manager must have
a connection manager name (see
Connection_Manager_Name for syntax).
The connection manager must then provide a well-known bus name of
org.freedesktop.Telepathy.ConnectionManager.cmname
where cmname is its connection manager name. If it makes sense
to start the connection manager using D-Bus service activation, it
must register that well-known name for service activation by installing
a .service file.
Clients can list the running connection managers by calling the
ListNames method on the D-Bus daemon's org.freedesktop.DBus interface
and looking for names matching the above pattern; they can list the
activatable connection managers by calling ListActivatableNames, and
they should usually combine the two lists to get a complete list of
running or activatable connection managers.
When the connection manager is running, it must have an object
implementing the ConnectionManager interface at the object path
/org/freedesktop/Telepathy/ConnectionManager/cmname.
Connection managers' capabilities can be determined dynamically by
calling their ListProtocols method, then
for each protocol of interest, calling
GetParameters to discover the required and
optional parameters.
However, since it is inefficient to activate all possible connection
managers on the system just to find out what they can do, there
is a standard mechanism to store static information about CMs in
".manager files".
To look up a connection manager's supported protocols, clients
should search the data directories specified by
the
freedesktop.org XDG Base Directory Specification ($XDG_DATA_HOME,
defaulting to $HOME/.local/share if unset, followed by
colon-separated paths from $XDG_DATA_DIRS, defaulting to
/usr/local/share:/usr/share if unset) for the first file named
telepathy/managers/cmname.manager that can be
read without error. This file has the same syntax as a
freedesktop.org Desktop Entry file.
Clients must still support connection managers for which no
.manager file can be found, which they can do by activating
the connection manager and calling its methods; the
.manager file is merely an optimization. Connection managers
whose list of protocols can change at any time (for instance, via
a plugin architecture) should not install a .manager
file.
For each protocol name proto that would be returned by
ListProtocols, the .manager file contains a group
headed [Protocol proto]. For each parameter
p that would be returned by GetParameters(proto), the
.manager file contains a key param-p with a value
consisting of a D-Bus signature (a single complete type), optionally
followed by a space and a space-separated list of flags. The supported
flags are:
required, corresponding to
Conn_Mgr_Param_Flag_Required
register, corresponding
to Conn_Mgr_Param_Flag_Register
secret, corresponding
to Conn_Mgr_Param_Flag_Secret
dbus-property, corresponding
to Conn_Mgr_Param_Flag_DBus_Property
The group may also contain a key default-p
whose value is a string form of the default value for the parameter.
If this key exists, it sets the default, and also sets the flag
Conn_Mgr_Param_Flag_Has_Default. The default value is formatted
according to the D-Bus signature as follows:
s (string)
The UTF-8 string, with the standard backslash escape
sequences supported by the Desktop Entry Specification
(the "localestring" type from the Desktop Entry Specification)
o (object path)
The object path as an ASCII string
b (boolean)
"true" (case-insensitively) or "1" means True, "false"
(case-insensitively) or "0" means False
y, q, u, t (8-, 16-, 32-, 64-bit unsigned integer)
ASCII decimal integer
n, i, x (16-, 32-, 64-bit signed integer)
ASCII decimal integer, optionally prefixed with "-"
d (double-precision floating point)
ASCII decimal number
as (array of string)
A sequence of UTF-8 strings each followed by a semicolon, with
any semicolons they contain escaped with a backslash
(the "localestrings" type from the Desktop Entry Specification)
Currently, no other D-Bus signatures are allowed to have default values,
but clients parsing the .manager file MUST ignore defaults
that they cannot parse, and treat them as if the
default-p key was not present at all.
It is not required that a connection manager be able to support multiple
protocols, or even multiple connections. When a connection is made, a
service name where the connection object can be found is returned. A
manager which can only make one connection may then remove itself from its
well-known bus name, causing a new connection manager to be activated when
somebody attempts to make a new connection.
s+ org.freedesktop.Telepathy.ConnectionManagert in_signaturet st
out_signatures a(susv)c C s
t d S( s
Get a list of the parameters which must or may be provided to the
RequestConnection method when connecting
to the given protocol,
or registering (the boolean "register" parameter is available,
and set to true).
N( t NotImplementedError( t selft Protocol( ( sK /usr/lib/python2.6/site-packages/telepathy/_generated/Connection_Manager.pyt
GetParameters s
t t asc C s
t d S( st
Get a list of protocol identifiers that are implemented by this
connection manager.
N( R ( R ( ( sK /usr/lib/python2.6/site-packages/telepathy/_generated/Connection_Manager.pyt
ListProtocols s s sa{sv}t soc C s
t d S( s
Request a
Connection
object representing a given account on a given
protocol with the given parameters. The method returns the bus name
and the object path where the new Connection object can be found,
which should have the status of Connection_Status_Disconnected, to
allow signal handlers to be attached before connecting is started
with the
Connect
method.
The parameters which must and may be provided in the parameters
dictionary can be discovered with the
GetParameters method. These
parameters, their types, and their default values may be cached
in files so that all available connection managers do not need to be
started to discover which protocols are available.
To request values for these parameters from the user, a client must
have prior knowledge of the meaning of the parameter names, so the
following well-known names and types should be used where appropriate:
account (s)
The identifier for the user's account on the server
server (s)
A fully qualified domain name or numeric IPv4 or IPv6 address.
Using the fully-qualified domain name form is recommended whenever
possible. If this parameter is specified and the account for that
protocol also specifies a server, this parameter should override
that in the user id.
port (q)
A TCP or UDP port number. If this parameter is specified and the
account for that protocol also specifies a port, this parameter
should override that in the account.
password (s)
A password associated with the account.
require-encryption (b)
Require encryption for this connection. A connection should fail
to connect if require-encryption is set and an encrypted connection
is not possible.
register (b)
This account should be created on the server if it does not
already exist.
ident (s)
The local username to report to the server if necessary, such as
in IRC.
fullname (s)
The user's full name if the service requires this when
authenticating or registering.
stun-server (s)
The IP address or FQDN of a STUN server to use for NAT traversal,
without any ":port" suffix.
stun-port (q)
The UDP port number on the stun-server to use for STUN. Only
significant if the stun-server is also supplied.
keepalive-interval (u)
The time in seconds between pings sent to the server to ensure
that the connection is still alive, or 0 to disable such
pings.
Every successful RequestConnection call will cause the emission of a
NewConnection signal for the same newly
created connection. The
requester can use the returned object path and service name
independently of the emission of that signal. In that case this signal
emission is most useful for, e.g. other processes that are monitoring
the creation of new connections.
N( R ( R R t
Parameters( ( sK /usr/lib/python2.6/site-packages/telepathy/_generated/Connection_Manager.pyt RequestConnection s Tt signaturet sosc C s d S( sQ
Emitted when a new Connection object
is created.
N( ( R t Bus_Namet Object_PathR ( ( sK /usr/lib/python2.6/site-packages/telepathy/_generated/Connection_Manager.pyt
NewConnection s ( t __name__t
__module__t __doc__t dbust servicet methodR R
R
t signalR ( ( ( sK /usr/lib/python2.6/site-packages/telepathy/_generated/Connection_Manager.pyR s
t' ' 'V( R t dbus.serviceR R t ObjectR ( ( ( sK /usr/lib/python2.6/site-packages/telepathy/_generated/Connection_Manager.pyt <module> s