I tend to agree on no longer using domains and just trying to restart the
process gracefully. The documentation seemed to imply that a new solution
was already in the works and I was curious as to what that solution was.
Thanks everyone for the answers
On Sunday, September 13, 2015 at 11:14:01
On Sun, Sep 13, 2015 at 5:37 AM, Charles Dumas wrote:
> I'm sorry if this has been discussed somewhere, but I can't seem to find it
> with google:
>
> I noticed the domain module is marked as deprecated in 4.0.0 :
> https://nodejs.org/api/domain.html
>
> The documentation isn't clear about what us
That's what the text you quoted says. It's not deprecated yet, but it will
be as soon as there is a replacement.
1. Pending deprecation, looking for an alternative <-- now
2. Deprecated, will print warnings if you use it<-- probably
not 4.x
3. Removed, will fail with undefined me
Here is the PR that made the change:
https://github.com/nodejs/node/pull/141
And here's an expanded explanation:
https://github.com/nodejs/node/pull/141#commitcomment-8951851
While not ideal, I can understand deprecating if you know a different
solution is needed, even if that solution isn't av
I'm sorry if this has been discussed somewhere, but I can't seem to find it
with google:
I noticed the domain module is marked as deprecated in 4.0.0
: https://nodejs.org/api/domain.html
The documentation isn't clear about what users should move to instead of
domains, just that they should be
