4 Commits (74ef94907277d8aa29d23cef29aee25161960376)

Author	SHA1	Message	Date
Ben Noordhuis	fb3ec32b0e	net: use close callback, not process.nextTick ... Don't emit the 'close' event with process.nextTick. Closing a handle is an operation that usually *but not always* completes on the next tick of the event loop, hence using process.nextTick is not reliable. Use a proper handle close callback and emit the 'close' event from inside the callback. Update tests that depend on the intricacies of the old model. Fixes #3459.	2013-03-06 16:15:18 +01:00
isaacs	4e5fe2d45a	nextTick: Handle tick callbacks after each tick	2012-07-16 21:05:10 -07:00
Ben Noordhuis	989ae81c71	test: fix simple/test-process-active-wraps ... Said test relies a great deal on internals and implementation details (I should know, I wrote it). Patch it up to work with libuv's new refcounting scheme.	2012-05-22 16:14:30 +02:00
Ben Noordhuis	5f0406534c	process: add _getActiveHandles(), _getActiveRequests() ... * process._getActiveHandles() returns a list containing all active handles (timers, sockets, etc.) that have not been unref'd. * process._getActiveRequests() returns a list of active requests (in-flight actions like connecting to a remote host, writing data to a socket, etc.).	2012-05-15 21:00:27 +02:00