diff --git a/docs/generated/interfaces/HttpResponse.html b/docs/generated/interfaces/HttpResponse.html index becc39c..8d251fd 100644 --- a/docs/generated/interfaces/HttpResponse.html +++ b/docs/generated/interfaces/HttpResponse.html @@ -4,7 +4,7 @@
Arbitrary user data may be attached to this object
Corking a response is a performance improvement in both CPU and network, as you ready the IO system for writing multiple chunks at once. By default, you're corked in the immediately executing top portion of the route handler. In all other cases, such as when returning from await, or when being called back from an async database request or anything that isn't directly executing in the route handler, you'll want @@ -15,7 +15,7 @@ in one TLS block being sent off, each with one send syscall.
res.cork(() => { res.writeStatus("200 OK").writeHeader("Some", "Value").write("Hello world!"); });
-Ends this response by copying the contents of body.
Returns the remote IP address in binary format (4 or 16 bytes), as reported by the PROXY Protocol v2 compatible proxy.
diff --git a/docs/generated/interfaces/WebSocket.html b/docs/generated/interfaces/WebSocket.html index 961afec..063946f 100644 --- a/docs/generated/interfaces/WebSocket.html +++ b/docs/generated/interfaces/WebSocket.html @@ -3,15 +3,15 @@ Read more about this in the user manual.Arbitrary user data may be attached to this object. In C++ this is done by using getUserData().
-Forcefully closes this WebSocket. Immediately calls the close handler. No WebSocket close message is sent.
-See HttpResponse.cork. Takes a function in which the socket is corked (packing many sends into one single syscall/SSL block)
-Gracefully closes this WebSocket. Immediately calls the close handler. A WebSocket close message is sent with code and shortMessage.
-Returns the bytes buffered in backpressure. This is similar to the bufferedAmount property in the browser counterpart. Check backpressure example.
Immediately force closes the connection. Any onAborted callback will run.
-