File: README.md

package info (click to toggle)
chromium 139.0.7258.127-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 6,122,156 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 (14 lines) | stat: -rw-r--r-- 801 bytes parent folder | download | duplicates (7) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
 
The root node of the class hierarchy for the code in this directory is
`BucketContext`. Start off by reading that class's documentation.

Each `BucketContext` and its owned objects are associated with a single
IndexedDB instance, such as that accessed via `navigator.indexedDB` or the
`indexedDB` for a [storage bucket](https://developer.chrome.com/docs/web-platform/storage-buckets).

Code in this directory mostly runs on the `SequencedTaskRunner` that is created
by the `IndexedDBContextImpl` for the `BucketContext` when the former
spawns the latter. This is sometimes referred to as the "bucket thread".

The only entry point into this directory that external code should access is
the `BucketContext`, but classes in this directory can use some thread-agnostic
code such as ../file_path_util.h.