Merge pull request #76 from foldlabs/jersey_upgrade

Introduce WebSocket endpoint for pushing events
events are sent to listening web socket
setup minimalist clojurescript project to build demo UI
added websocket client handler skeleton
change executable
preparing demo
properly encode ws messages as UTF-8

Looks like sending plain strings just use the bytes as-is which does not seem to make
Chrome API on the client side.
Client-side still not showing messages properly, got an integer length instead???
first working UI: client connects in ws to server and can display messages
boostrapize UI
send WS messages in Json format
make UI more attractive

* replace bootstrap with pure
* limit evetns to 15
* display events most recent first
* display events in table
added protocol listener logic to Raft context

listeners can now be notified of incoming events. Note this might introduce the possibility of refactoring the code
to ensure all operations goes through listening logic, decoupling execution from interface a little bit more.
wire protocol listeners into modules and context

websocket emitter implements RaftProtocolListener but is currently no-op
ws listener actually send protocol events to clients
remove dummy messages
test and fix UI for demo

remove dot in messages types names to be able to use them as class names in interface
fix error in disconnect
format messages according to structure
extracted messaging logic from core to own ns
extracted messages table to own component
more idiomatic selection of messages
expose configuration as a HTTP resource