File: README.md

package info (click to toggle)
chromium 138.0.7204.183-1~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-proposed-updates
  • size: 6,080,960 kB
  • sloc: cpp: 34,937,079; ansic: 7,176,967; javascript: 4,110,704; python: 1,419,954; asm: 946,768; xml: 739,971; pascal: 187,324; sh: 89,623; perl: 88,663; objc: 79,944; sql: 50,304; cs: 41,786; fortran: 24,137; makefile: 21,811; php: 13,980; tcl: 13,166; yacc: 8,925; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (31 lines) | stat: -rw-r--r-- 1,007 bytes parent folder | download | duplicates (6) 
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
 
Chrome Remote Desktop
---------------------


This directory contains the code that controls the remote admin triggered
Chrome Remote Desktop (CRD) sessions.

These sessions are started through a remote command (sent from the DPanel
devices page).

Remote Commands
---------------

There are 2 remote commands involved in starting CRD sessions:

  * FETCH_CRD_AVAILABILITY_INFO: This command queries the state
    of the device, and returns if CRD sessions are possible and if not, why.
  * START_CRD_SESSION: This command actually starts a CRD session.

Public APIs
-----------

The public API of this folder exists out of 3 classes:

  * `DeviceCommandFetchCrdAvailabilityInfoJob`: The `RemoteCommandJob` that handles the
    FETCH_CRD_AVAILABILITY_INFO remote command.
  * `DeviceCommandStartCrdSessionJob`: The `RemoteCommandJob` that handles the
    START_CRD_SESSION remote command.
  * `CrdAdminSessionController`: The long-lived controller that keeps track of
    the currently active CRD session.