domain-middleware
domain-middleware copied to clipboard
expressjs
`uncaughtException` middleware for connect, base on `domain` module.
``` var http = require('http'); var connect = require('connect'); var domainMiddleware = require('domain-middleware'); var server = http.createServer(); var app = connect() .use( domainMiddleware({ server: server, killTimeout: 30000, }), ) .use(function...
@fengmk2 - you have been identified as the last / most active committer in this repo which is inactive for a while. This ping is to check with you to...
I created something similar to this middleware, not sure how similar or different expressjs/domain-middleware is, but since this repo hasn't been touched in ~5 years maybe time for some freshness?...
Just adding contributing instructions. Also an .editorconfig, it doesn't hurt.
Seems domain-middleware was moved, but the readme wasn't updated. Fixed. Updated links. Removed outdated info.
fixes #5, #6, #7
pick feature from HabitRPG fork, LGTM https://github.com/HabitRPG/domain-middleware
instead of try/catching `server.close` and `worker.disconnect`, we could listen to their `close` and `disconnect` signal and abstain from repeating if already closed / shut. More elegant I think. PR pending.
According to node documentation, calling `worker.disconnect()` will close existing servers. And that's true (tested it) Calling `worker.disconnect()`will even throw an uncaught if the servers are already closed (tested it also)....