Logging, socket-cluster compatibility, performance, error-handling

[rasmuserik]

Several changes on the way to fix DBCDK/mobilsoeg#5:

• use io.on instead of io.use as the latter seems to be socket.io only
• add logging (also useful for profiling later on)
• do not try to emit cyclic error-datastructure

Do we know the structure of the error sent to the serviceprovider dispatch? Ie. does it always have a type/body/... (we cannot emit it as it is cyclic, but if we know something about it, we could give more info than just that an error occurred).

I will update the code with a bit more info in what is logged/emitted later.

[rasmuserik]

Removed the parameters passed to logging Transform has been triggered, as these were a source of performance issues in mobilsoeg.

This pull-request is a work in progress. I will figure out which data are small enough to log, and also fix the tests, and unfinished tasks above.

[rasmuserik]

The pull request should be ready to merge now. Content:

• better error reporting (errors with cyclic references, possibly on prototype, was never serialised/sent to client, - now they are)
• performance fix (serialising large objects for logging was the source of performance problems)
• socketcluster compatibility (use io.on instead of io.use which is socket.io only)
• add more logging (warning when the request fails, and timing of request)
• cleanup (only Dispatcher.js instead of both dispatcher.js and Dispatcher.js)