websocket-driver 0.5.1-java → 0.5.2-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9309a5e07cfe961676a86f4a69ea5d1259e108f1
-  data.tar.gz: 74ad3723262d26e0d97d7cf457b0ea103fe3849d
+  metadata.gz: 204e724cade4affb9fa01f98056d0c36e62af18e
+  data.tar.gz: 08b5f37a0e84ae7b241cec00f72814ccf3653018
 SHA512:
-  metadata.gz: cee6af332c646c9576a01e977c71a9c3da7907c542797c24f8c306fedad6cc442407cfcd9363cc4464408b98c129d45912ad40327045a503cb00c94aa2f6099b
-  data.tar.gz: 7150f3ddcbbe15aa39202ae2553f029bebae510c852ca35a63b4f9811d8570c2b781e607b8a31b4271c4015d4cce5d7b63fba0e331abbaef01a4f1e938b77c5d
+  metadata.gz: 7de37329327a3dc0af08de66c4fa6eed954fb99a77b0995f3332ffc332470519d2a64aef07337672553a53308fda349c325497b9cf9d6b1e81f50ff8843d9b6c
+  data.tar.gz: 9f19147ee7a20731507567a2670836da31c67664eee4abdd94b54afded93f44130ebf905ff2353bdae602f6acc6982fb9d1d814a00c99c3c37eac3364037815e

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+### 0.5.2 / 2015-02-19
+
+* Don't emit multiple `error` events
+
 ### 0.5.1 / 2014-12-18
 
 * Don't allow drivers to be created with unrecognized options

data/README.md

@@ -7,8 +7,8 @@ code to stream data in and out of it without needing to know anything about how
 the protocol actually works. Think of it as a complete WebSocket system with
 pluggable I/O.
 
-Due to this design, you get a lot of things for free. In particular, if you
-hook this module up to some I/O object, it will do all of this for you:
+Due to this design, you get a lot of things for free. In particular, if you hook
+this module up to some I/O object, it will do all of this for you:
 
 * Select the correct server-side driver to talk to the client
 * Generate and send both server- and client-side handshakes
@@ -68,8 +68,8 @@ Server-side sockets require one additional method:
 
 To handle a server-side WebSocket connection, you need to check whether the
 request is a WebSocket handshake, and if so create a protocol driver for it.
-You must give the driver an object with the `env`, `url` and `write` methods.
-A simple example might be:
+You must give the driver an object with the `env`, `url` and `write` methods. A
+simple example might be:
 
 ```ruby
 require 'websocket/driver'
@@ -172,9 +172,9 @@ EM.run {
 ```
 
 In the `:connect` event, `@driver.env` is a Rack env representing the request.
-If the request has a body, it will be in the `@driver.env['rack.input']`
-stream, but only as much of the body as you have so far routed to it using the
-`parse` method.
+If the request has a body, it will be in the `@driver.env['rack.input']` stream,
+but only as much of the body as you have so far routed to it using the `parse`
+method.
 
 
 ### Client-side
@@ -251,11 +251,11 @@ driver = WebSocket::Driver.server(socket, options)
 driver = WebSocket::Driver.client(socket, options)
 ```
 
-The `rack` method returns a driver chosen using the socket's `env`. The
-`server` method returns a driver that will parse an HTTP request and then
-decide which driver to use for it using the `rack` method. The `client` method
-always returns a driver for the RFC version of the protocol with masking
-enabled on outgoing frames.
+The `rack` method returns a driver chosen using the socket's `env`. The `server`
+method returns a driver that will parse an HTTP request and then decide which
+driver to use for it using the `rack` method. The `client` method always returns
+a driver for the RFC version of the protocol with masking enabled on outgoing
+frames.
 
 The `options` argument is optional, and is a hash. It may contain the following
 keys:
@@ -279,9 +279,9 @@ Sets the callback block to execute when the socket becomes open.
 
 #### `driver.on('message') { |event| }`
 
-Sets the callback block to execute when a message is received. `event` will
-have a `data` attribute containing either a string in the case of a text
-message or an array of integers in the case of a binary message.
+Sets the callback block to execute when a message is received. `event` will have
+a `data` attribute containing either a string in the case of a text message or
+an array of integers in the case of a binary message.
 
 #### `driver.on('error') { |event| }`
 
@@ -304,8 +304,8 @@ framework.
 #### `driver.set_header(name, value)`
 
 Sets a custom header to be sent as part of the handshake response, either from
-the server or from the client. Must be called before `start`, since this is
-when the headers are serialized and sent.
+the server or from the client. Must be called before `start`, since this is when
+the headers are serialized and sent.
 
 #### `driver.start`
 
@@ -341,8 +341,8 @@ ping/pong.
 
 #### `driver.close`
 
-Initiates the closing handshake if the socket is still open. For drivers with
-no closing handshake, this will result in the immediate execution of the
+Initiates the closing handshake if the socket is still open. For drivers with no
+closing handshake, this will result in the immediate execution of the
 `on('close')` callback. For drivers with a closing handshake, this sends a
 closing frame and `emit('close')` will execute when a response is received or a
 protocol error occurs.
@@ -355,30 +355,29 @@ Returns the WebSocket version in use as a string. Will either be `hixie-75`,
 #### `driver.protocol`
 
 Returns a string containing the selected subprotocol, if any was agreed upon
-using the `Sec-WebSocket-Protocol` mechanism. This value becomes available
-after `emit('open')` has fired.
+using the `Sec-WebSocket-Protocol` mechanism. This value becomes available after
+`emit('open')` has fired.
 
 
 ## License
 
 (The MIT License)
 
-Copyright (c) 2010-2014 James Coglan
+Copyright (c) 2010-2015 James Coglan
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of
 this software and associated documentation files (the 'Software'), to deal in
 the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
-of the Software, and to permit persons to whom the Software is furnished to do
-so, subject to the following conditions:
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
 
 The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/lib/websocket/driver/hybi.rb

@@ -255,6 +255,7 @@ module WebSocket
       end
 
       def fail(type, message)
+        return if @ready_state > 1
         emit(:error, ProtocolError.new(message))
         shutdown(ERRORS[type], message)
       end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: websocket-driver
 version: !ruby/object:Gem::Version
-  version: 0.5.1
+  version: 0.5.2
 platform: java
 authors:
 - James Coglan
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2014-12-18 00:00:00.000000000 Z
+date: 2015-02-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: websocket-extensions