What is the job of monitor.js

[mschaaf]

Hej,

we use polo in a node-webkit project and have issues starting the monitor.js daemon from within node-webkit. The issue lays on the node-webkit site. See nwjs/nw.js#213 for it.

Our application seems to work fine without it. But before turning it off in production we want to be sure that we understand the aim of this daemon correctly. So that we know what functionality we and how we can circumvent if necessary the daemon behavior.

It seems to us that it deregisters a client from all other clients that know about it. Right?

Thank you for your help.

[mafintosh]

Yes you're right. Do you have a link to your app? (curious :))

The aim of the monitor is to detect if a service crashes without having to wait for it to timeout.
There shouldnt be any problems in turning it off.

I'll probably factor it out in a new release.

[mschaaf]

https://github.com/Dica-Developer/quickQuestion