README.md in em-websocket-0.2.1 vs README.md in em-websocket-0.3.0

@@ -40,9 +40,25 @@
         }
     }) do |ws|
     ...
     end
 
+## Handling errors
+
+There are two kinds of errors that need to be handled - errors caused by incompatible WebSocket clients sending invalid data and errors in application code. They are handled as follows:
+
+Errors caused by invalid WebSocket data (for example invalid errors in the WebSocket handshake or invalid message frames) raise errors which descend from `EventMachine::WebSocket::WebSocketError`. Such errors are rescued internally and the WebSocket connection will be closed immediately or an error code sent to the browser in accordance to the WebSocket specification. However it is possible to be notified in application code on such errors by including an `onerror` callback.
+
+    ws.onerror { |error|
+      if e.kind_of?(EM::WebSocket::WebSocketError)
+        ...
+      end
+    }
+
+Application errors are treated differently. If no `onerror` callback has been defined these errors will propagate to the EventMachine reactor, typically causing your program to terminate. If you wish to handle exceptions, simply supply an `onerror callback` and check for exceptions which are not decendant from `EventMachine::WebSocket::WebSocketError`.
+
+It is also possible to log all errors when developing by including the `:debug => true` option when initialising the WebSocket connection.
+
 ## Examples & Projects using em-websocket
 
 * [Pusher](http://pusherapp.com) - Realtime client push
 * [Livereload](https://github.com/mockko/livereload) - LiveReload applies CSS/JS changes to Safari or Chrome w/o reloading
 * [Twitter AMQP WebSocket Example](http://github.com/rubenfonseca/twitter-amqp-websocket-example)
\ No newline at end of file