anchor.diff:  The sample application is deployed as a WAR outcome of a build with Apache Maven.
   In addition to the traditional management WebSocket lifecycle, the sending messages workflow is as follows :
   
  -* at each point of the match, 'peers clients' receive data match (score, service...)
  +* each 'peer client' can connect to 1 or 4 lives
  +* each 'peer client' can disconnect from a match
  +* at each point of a match, clients which are connected to this match, will receive datas (score, service...)
   * the 'peer client' may send a message to bet on the winner of the match
  -* at the end of the match, 'peers client' receive a message containing the name of the winner
  +* each time that one 'peer client' bet on a match, all others 'peers clients' which have bet on the same match, will receive a message with the total number of bettors
  +* at the end of the match, 'peers client' receive a message containing the name of the winner and a specific message if they bet on this match
   
   *All messages are exchanged in JSON format* + 
   
  
positive.code: Once the *handshake* is approved, the use of WebSocket protocol is established. There are an open connection on the 'peer server side' as well on the 'peer client side', callback handlers are called to initiate the communication. + 
  The *Data transfer* can now begin, so the 2 peers can exchange messages in a bidirectionnal and full-duplex communication.
  
  As shown in the diagram named *Figure 3*, the +peer server+ can send multiple messages ('in this example : 1 message to each point of the game') without any +peer client+ response and the peer client can also send messages at any time ('in this example : betting on the winner of the match').
  Each peer can send a specific message to close the connection. +
  
  With Java EE7 Platform, the +peer server side+ code is written in *Java* while the +peer client side+ code is in *Java or Javascript*.
  
  === Closing Handshake
  
  This phase can be initiated by both peer. A peer that want to close the communication need to send a close control frame and it will received a close control frame too as a response.
  
  == WebSocket Javascript API (Client)
  
  
negative.code: 
  As shown in the diagram below, the *WebSocket protocol works in two phases* named :
  
  . *+handshake+ (open and close)*
  . *+data transfer+*
  
  [[websocket_protocol]]
  