diff options
author | William Jon McCann <jmccann@redhat.com> | 2008-07-30 17:37:24 -0400 |
---|---|---|
committer | William Jon McCann <jmccann@redhat.com> | 2008-07-30 17:37:24 -0400 |
commit | edad750e967458f55b9e761af966f325213ce9fe (patch) | |
tree | d068c3e14113e3c6067185b4f5e25ef219438273 /doc/xml/ck-terms.xml | |
parent | 77fe8e2e89af7cd21357116e9668b23d958fb2a5 (diff) |
reorganize the docs a bit
Diffstat (limited to 'doc/xml/ck-terms.xml')
-rw-r--r-- | doc/xml/ck-terms.xml | 67 |
1 files changed, 0 insertions, 67 deletions
diff --git a/doc/xml/ck-terms.xml b/doc/xml/ck-terms.xml deleted file mode 100644 index d3d544d..0000000 --- a/doc/xml/ck-terms.xml +++ /dev/null @@ -1,67 +0,0 @@ -<chapter id="terms"> - <title>Terminology</title> - - <sect1> - <title>Session</title> - <para> -A session is a collection of all processes that share knowledge of a -secret. In the typical (or ideal) case, these processes all originate -from a single common ancestor. - </para> - <para> -As an implementation detail, for now, this secret should be stored in -the process environment by the session leader under the name -XDG_SESSION_COOKIE. When and if we are able to take advantage of a -mechanism in the underlying system to store session registration -information - we will. However, such a mechanism is not known at the -present time. - </para> - <para> -Using an environment variable does have certain advantages. For one, -it is quite easy for a process to opt-out of a Session by simply -unsetting the XDG_SESSION_COOKIE variable. - </para> - <para> -Limitations of using an environment variable implementation include -not being able to strictly limit visibility of the secret to a particular -process ancestry. So, it is not possible to enforce session boundaries -other than on a per-user basis. For example, we don't yet have a way -to prevent a process from moving between sessions owned by the same -user. - </para> - </sect1> - - <sect1> - <title>Session leader</title> - <para> -The session leader is the process that requests that a new session be -opened. It does this by connecting to the D-Bus system bus and using -either org.freedesktop.ConsoleKit.Manager.OpenSession() or -org.freedesktop.ConsoleKit.Manager.OpenSessionWithParameters(). The session -that it registers will remain open until the connection to the system -bus is lost or it calls org.freedesktop.ConsoleKit.Manager.CloseSession(). - </para> - <para> -The session leader is the only process for which CloseSession() will -be allowed. - </para> - </sect1> - - <sect1> - <title>Seat</title> - <para> -A seat is a collection of sessions and a set of hardware (usually at -least a keyboard and mouse). Only one session may be active on a -seat at a time. - </para> - <para> -At the present time, all Sessions that are considered "local" to -a system will be added the the first Seat and every other Session -will be added to its own Seat. - </para> - <para> -True, hardware, multi-seat capabilities will be added in a later release. - </para> - </sect1> - -</chapter> |