Improved ws-reconnecting.js send() error handling

  WebSocket is already in CLOSING or CLOSED state. convos-f3cb4173e1b5b54a879ba8f8335b7b95.js:456
    ReconnectingWebSocket.send convos-f3cb4173e1b5b54a879ba8f8335b7b95.js:456
    $input.send convos-f3cb4173e1b5b54a879ba8f8335b7b95.js:498
    (anonymous function) convos-f3cb4173e1b5b54a879ba8f8335b7b95.js:496
    handleObj.handler convos-f3cb4173e1b5b54a879ba8f8335b7b95.js:26
    x.event.dispatch convos-f3cb4173e1b5b54a879ba8f8335b7b95.js:3
    v.handle convos-f3cb4173e1b5b54a879ba8f8335b7b95.js:3

  So it seems that send() failed badly when the other end shut down the
  connnection.

  .---------------------------------------------------------------.
  | 3 | Connection Close Frame (Opcode 8, mask) |  0 | 4:23:52 PM |
  | 2 | <div class="pong"/>                     | 19 | 4:22:52 PM |
  | 1 | <div class="ping"/>                     | 19 | 4:22:52 PM |
  '---------------------------------------------------------------'
Let the javascript send ping instead of the server
Fix format_conversation(...)
Fix javascript typos
Fix resending buffer over websocket
Fix typo (thanks DominikTo)
Let's not be so eager to refresh()
Made pong.html.ep smaller
Merge pull request #85 from Nordaaker/improvement/ping-pong

Improvement/ping pong