| moz.build |
|
853 |
| osfile_async_front.jsm |
Asynchronous front-end for OS.File.
This front-end is meant to be imported from the main thread. In turn,
it spawns one worker (perhaps more in the future) and delegates all
disk I/O to this worker.
Documentation note: most of the functions and methods in this module
return promises. For clarity, we denote as follows a promise that may resolve
with type |A| and some value |value| or reject with type |B| and some
reason |reason|
@resolves {A} value
@rejects {B} reason
|
50004 |
| osfile_async_worker.js |
eslint-env worker |
14087 |
| osfile_native.jsm |
Native (xpcom) implementation of key OS.File functions
|
3909 |
| osfile_shared_allthreads.jsm |
OS.File utilities used by all threads.
This module defines:
- logging;
- the base constants;
- base types and primitives for declaring new types;
- primitives for importing C functions;
- primitives for dealing with integers, pointers, typed arrays;
- the base class OSError;
- a few additional utilities.
|
37084 |
| osfile_shared_front.js |
Code shared by OS.File front-ends.
This code is meant to be included by another library. It is also meant to
be executed only on a worker thread.
|
20698 |
| osfile_unix_allthreads.jsm |
This module defines the thread-agnostic components of the Unix version
of OS.File. It depends on the thread-agnostic cross-platform components
of OS.File.
It serves the following purposes:
- open libc;
- define OS.Unix.Error;
- define a few constants and types that need to be defined on all platforms.
This module can be:
- opened from the main thread as a jsm module;
- opened from a chrome worker through require().
|
10350 |
| osfile_unix_back.js |
eslint-env mozilla/chrome-worker, node |
29003 |
| osfile_unix_front.js |
Synchronous front-end for the JavaScript OS.File library.
Unix implementation.
This front-end is meant to be imported by a worker thread.
|
44318 |
| osfile_win_allthreads.jsm |
This module defines the thread-agnostic components of the Win version
of OS.File. It depends on the thread-agnostic cross-platform components
of OS.File.
It serves the following purposes:
- open kernel32;
- define OS.Shared.Win.Error;
- define a few constants and types that need to be defined on all platforms.
This module can be:
- opened from the main thread as a jsm module;
- opened from a chrome worker through require().
|
11307 |
| osfile_win_back.js |
This file can be used in the following contexts:
1. included from a non-osfile worker thread using importScript
(it serves to define a synchronous API for that worker thread)
(bug 707681)
2. included from the main thread using Components.utils.import
(it serves to define the asynchronous API, whose implementation
resides in the worker thread)
(bug 729057)
3. included from the osfile worker thread using importScript
(it serves to define the implementation of the asynchronous API)
(bug 729057)
|
15733 |
| osfile_win_front.js |
Synchronous front-end for the JavaScript OS.File library.
Windows implementation.
This front-end is meant to be imported by a worker thread.
|
47897 |
| ospath_unix.jsm |
Handling native paths.
This module contains a number of functions destined to simplify
working with native paths through a cross-platform API. Functions
of this module will only work with the following assumptions:
- paths are valid;
- paths are defined with one of the grammars that this module can
parse (see later);
- all path concatenations go through function |join|.
|
5675 |
| ospath_win.jsm |
Handling native paths.
This module contains a number of functions destined to simplify
working with native paths through a cross-platform API. Functions
of this module will only work with the following assumptions:
- paths are valid;
- paths are defined with one of the grammars that this module can
parse (see later);
- all path concatenations go through function |join|.
Limitations of this implementation.
Windows supports 6 distinct grammars for paths. For the moment, this
implementation supports the following subset:
- drivename:backslash-separated components
- backslash-separated components
- \\drivename\ followed by backslash-separated components
Additionally, |normalize| can convert a path containing slash-
separated components to a path containing backslash-separated
components.
|
10418 |
| ospath.jsm |
Handling native paths.
This module contains a number of functions destined to simplify
working with native paths through a cross-platform API. Functions
of this module will only work with the following assumptions:
- paths are valid;
- paths are defined with one of the grammars that this module can
parse (see later);
- all path concatenations go through function |join|.
|
1491 |