Cleaned up rest interface, now it should behave correctly.

Tests are still in the making.
Rest interface is complete and working.

Next is WebSocket, as real-time PUB-SUB interface
Added frame for websocket implementation.

It seems I need a little bit of client management there, it's all minor though
Added full implementation of websocket.

Test still has to be written, should be simple
For some reason, the websocket closes itself after the first byte-write.

Either I try the gorilla implementation, or ... I figure out
what's wrong.
From the examples, I see no fault. Also there are no errors when dialing in.
It seems to work until someone tries to write it.
Will just use the gorilla one ...

... better than finding out that the socket implementation is just
somewhat broken ... lets see where the issue is.
And of course, let's hope gorilla doesn't show similar issues.
Minimal changes, better code, and gorilla works.

I believe the problem was that the Reader and Writer interface
provided by the google implementation didn't actually behave
similar to their normal counterparts due to the message based system
that is part of a websocket.
Reorganized temporal statistics handling

Now it's cleaner and allows all the code to be shared, without
reducing control about what to do with these messages.
Definitely better than before.
Added event to indicate the operation is starting.

That way, clients can prepare for the first actual result to appear.