fulmine.js 5.19.1 → 5.19.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -32,7 +32,7 @@ See [Migrating](#migrating) for what it handles and what it deliberately does no
|
|
|
32
32
|
|
|
33
33
|
[](https://www.npmjs.com/package/fulmine.js)
|
|
34
34
|
[](https://nodejs.org)
|
|
35
|
-
[](https://www.http-arena.com/#tuned=0)
|
|
35
|
+
[](https://www.http-arena.com/#tuned=0)
|
|
36
36
|
[](https://coveralls.io/github/nigrosimone/fulmine.js?branch=main)
|
|
37
37
|
[](https://github.com/nigrosimone/fulmine.js/actions/workflows/codeql.yml)
|
|
38
38
|
[](https://scorecard.dev/viewer/?uri=github.com/nigrosimone/fulmine.js)
|
|
@@ -624,6 +624,8 @@ app.listen(3000, () => console.log(`worker ${process.pid} listening`));
|
|
|
624
624
|
|
|
625
625
|
Anything held per process is now held per worker: an in-memory cache, a rate-limit counter, a session store or a `Map` of connected sockets is not shared, and needs Redis or something like it to be. `app.close()` in the primary stops the workers, and a `SIGTERM` or `SIGINT` that reaches only the primary, which is what a container sends, is passed on to them. Runnable: [`examples/cluster.js`](./examples/cluster.js).
|
|
626
626
|
|
|
627
|
+
10. `app.set("connection headers", false)` stops `Connection: keep-alive` and `Keep-Alive: timeout=10` going out on every response. Express sends both, so Fulmine sends both by default. An HTTP/1.1 connection stays open without being told, so to an HTTP/1.1 client the two headers say nothing it does not know already, and they cost 46 bytes and two header writes per response. A request that asked for `Connection: close` still gets `Connection: close`, and the connection is closed. Turn it off for an API behind a proxy or serving HTTP/1.1 clients; keep the default where a client or a proxy relies on the header to keep the connection open. Worth 2% to 3.5% here on a route that is not compiled, plus the bytes.
|
|
628
|
+
|
|
627
629
|
## WebSockets
|
|
628
630
|
|
|
629
631
|
`app.ws()` registers a WebSocket route, served by µWS itself. The upgrade never reaches node, so `server.on("upgrade")` and the libraries built on it have nothing to hear; this is the replacement.
|