File: README.md

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; 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.