extracted Application object for reuse into other Jersey containers
upgraded Jersey to latest version and deprecated JDK 6 support

* Jersey 2.8 requires Java 7
* replaced jdk6 with jdk8
added Jetty-based server

Use Jetty to expose events stream through webSocket endpoint
factorize basic HttpServer test for Jetty and Jdk
failed ws init event test
introduce module for injecting multiple listeners through guice

* cleanup log directories of launched servers after test to prevent server tests from impacting one another
properly stop server and application
remove invalid jdk8 travis target
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.