6184a70ba4
The upstream gcp aggressively closes the connection once it has received Content-Length bytes. However the @google-cloud/storage module doesn't handle this well and emits no event in this case. We were setting Content-Length because it's slightly more efficient and was important for our download progress bar (not anymore). The download should function fine without setting the Content-Length, and allows the storage stream to finish before closing the upstream socket. |
||
|---|---|---|
| .. | ||
| pages | ||
| routes | ||
| templates | ||
| .eslintrc.yml | ||
| api.js | ||
| base.css | ||
| dragManager.js | ||
| experiments.js | ||
| fileManager.js | ||
| fileReceiver.js | ||
| fileSender.js | ||
| keychain.js | ||
| main.css | ||
| main.js | ||
| metrics.js | ||
| ownedFile.js | ||
| pasteManager.js | ||
| readme.md | ||
| storage.js | ||
| utils.js | ||
Application Code
app/ contains the browser code that gets bundled into app.[hash].js. It's got all the logic, crypto, and UI. All of it gets used in the browser, and some of it by the server for server side rendering.
The main entrypoint for the browser is main.js and on the server routes/index.js gets imported by /server/routes/pages.js
pagescontains display logic an markup for pagesroutescontains route definitions and logictemplatescontains ui elements smaller than pages