diff options
| author | Sam Wilkins <samwilkins333@gmail.com> | 2020-01-11 17:58:16 -0500 |
|---|---|---|
| committer | Sam Wilkins <samwilkins333@gmail.com> | 2020-01-11 17:58:16 -0500 |
| commit | dc51ee0dc771b3ac6ff6adc7c039df94935ef943 (patch) | |
| tree | 9fd2c2abca48cf96ec6d2dc13f3236a1f14aee98 /src/server/session/README.txt | |
| parent | 791499af4f474fe8ec7863ab9fe7b5b1120ac5ce (diff) | |
switched out to npm
Diffstat (limited to 'src/server/session/README.txt')
| -rw-r--r-- | src/server/session/README.txt | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/src/server/session/README.txt b/src/server/session/README.txt deleted file mode 100644 index ac7d3d4e7..000000000 --- a/src/server/session/README.txt +++ /dev/null @@ -1,11 +0,0 @@ -/** - * These abstractions rely on NodeJS's cluster module, which allows a parent (master) process to share - * code with its children (workers). A simple `isMaster` flag indicates who is trying to access - * the code, and thus determines the functionality that actually gets invoked (checked by the caller, not internally). - * - * Think of the master thread as a factory, and the workers as the helpers that actually run the server. - * - * So, when we run `npm start`, given the appropriate check, initializeMaster() is called in the parent process - * This will spawn off its own child process (by default, mirrors the execution path of its parent), - * in which initializeWorker() is invoked. - */
\ No newline at end of file |
