0.9: Remove process.EventEmitter usage for Node 7.x

[jchv]

The kind of change this PR does introduce

• a bug fix
• a new feature
• an update to the documentation
• a code change that improves performance
• other

Current behaviour

Socket.IO 0.9.x does not work in Node.JS 7.0 due to the removal of process.EventEmitter. A myriad of existing software depends on Socket.IO 0.9.x, therefore it will either be necessary to update Socket.IO 0.9.x, or fork it. Some existing software still using 0.9.x includes the Yez extension for Google Chrome + corresponding Node.JS application.

New behaviour

This patch changes usages of process.EventEmitter to require('events').

[darrachequesne]

Hi! Would you know why the travis build fails?

[jchv]

Not really sure. My guess would be that the ancient version of Node in this branch is not new enough to install the dependencies anymore. Should I bump it to something newer? 0.12, maybe?

[darrachequesne]

Did you try with 0.10 or 0.12? It seems the tests are run with nodejs 0.6..

[jchv]

It's proving difficult to try to finagle things into a working state. Socket.IO depends on Expresso, a library that has been dead since around Socket.IO 0.9's time. I'm also seeing trouble with building Microtime, even if I update the package.json, which seems odd since it switched to node-gyp in 0.3.0.

It's worth noting that the difficulty is limited to testing. The library does function, at least on versions of Node.JS that have the event module.

[thegiantbeast]

+1 for patching this issue.

[darrachequesne]

Merged as 9ad1fd2, and released as 0.9.18. Thanks!