Make setImmediate have the same side effect with upstream node.
This commit is contained in:
parent
c87b21148c
commit
998e9792fb
1 changed files with 13 additions and 3 deletions
|
@ -22,9 +22,19 @@ globalPaths.push path.join(process.resourcesPath, 'app')
|
||||||
# Expose global variables.
|
# Expose global variables.
|
||||||
global.require = require
|
global.require = require
|
||||||
global.module = module
|
global.module = module
|
||||||
global.setImmediate = ->
|
|
||||||
process.activateUvLoop()
|
# setImmediate and process.nextTick makes use of uv_check and uv_prepare to
|
||||||
timers.setImmediate.apply this, arguments
|
# run the callbacks, however since we only run uv loop on requests, the
|
||||||
|
# callbacks wouldn't be called until something else activated the uv loop,
|
||||||
|
# which would delay the callbacks for arbitrary long time. So we should
|
||||||
|
# initiatively activate the uv loop once setImmediate and process.nextTick is
|
||||||
|
# called.
|
||||||
|
wrapWithActivateUvLoop = (func) ->
|
||||||
|
->
|
||||||
|
process.activateUvLoop()
|
||||||
|
func.apply this, arguments
|
||||||
|
process.nextTick = wrapWithActivateUvLoop process.nextTick
|
||||||
|
global.setImmediate = wrapWithActivateUvLoop timers.setImmediate
|
||||||
global.clearImmediate = timers.clearImmediate
|
global.clearImmediate = timers.clearImmediate
|
||||||
|
|
||||||
# Set the __filename to the path of html file if it's file:// protocol.
|
# Set the __filename to the path of html file if it's file:// protocol.
|
||||||
|
|
Loading…
Add table
Reference in a new issue