hakutaku/tdesktop
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

init
Some checks failed
Docker. / Ubuntu (push) Has been cancelled
Details
User-agent updater. / User-agent (push) Failing after 15s
Details
Lock Threads / lock (push) Failing after 10s
Details
Waiting for answer. / waiting-for-answer (push) Failing after 22s
Details
Needs user action. / needs-user-action (push) Failing after 8s
Details
Can't reproduce. / cant-reproduce (push) Failing after 8s
Details
Close stale issues and PRs / stale (push) Has been cancelled
Details

Browse Source
This commit is contained in:
allhaileris
2026-02-16 15:50:16 +03:00
commit afb81b8278
13816 changed files with 3689732 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
Telegram/ThirdParty/xdg-desktop-portal/doc/sessions.rst vendored Normal file
View File

@@ -0,0 +1,13 @@
Sessions
========
Some portal requests are connected to each other and need to be used in
sequence. The pattern used in such cases is a :ref:`Session <org.freedesktop.portal.Session>`
object. Just like :ref:`Request <org.freedesktop.portal.Request>`\s, sessions are
represented by an object path, that is returned by the initial ``CreateSession``
call of the respective portal. Subsequent calls take the object path of the
session they operate on as an argument.
Sessions can be ended from the application side by calling the ``Close()`` method
on the session. They can also be closed from the service side, in which case the
``::Closed`` signal is emitted on the Session object to inform the application.