websocket-driver - npm Package Versions - Socket

Sign in Demo Install

websocket-driver

Package Overview

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Previous 13 Next

0.5.4

published 0.5.4 • 9 years ago

Changelog

0.5.4 / 2015-03-29

Don't emit extra close frames if we receive a close frame after we already sent one
Fail the connection when the driver receives an invalid Sec-WebSocket-Extensions header

0.5.3

published 0.5.3 • 9 years ago

Changelog

0.5.3 / 2015-02-22

Don't treat incoming data as WebSocket frames if a client driver is closed before receiving the server handshake

0.5.2

published 0.5.2 • 9 years ago

Changelog

0.5.2 / 2015-02-19

Fix compatibility with the HTTP parser on io.js
Use websocket-extensions to make sure messages and close frames are kept in order
Don't emit multiple error events

0.5.1

published 0.5.1 • 9 years ago

Changelog

0.5.1 / 2014-12-18

Don't allow drivers to be created with unrecognized options

0.5.0

published 0.5.0 • 9 years ago

Changelog

0.5.0 / 2014-12-13

Support protocol extensions via the websocket-extensions module

0.4.0

published 0.4.0 • 9 years ago

Changelog

0.4.0 / 2014-11-08

Support connection via HTTP proxies using CONNECT

0.3.6

published 0.3.6 • 10 years ago

Changelog

0.3.6 / 2014-10-04

It is now possible to call close() before start() and close the driver

0.3.5

published 0.3.5 • 10 years ago

Changelog

0.3.5 / 2014-07-06

Don't hold references to frame buffers after a message has been emitted
Make sure that protocol and version are exposed properly by the TCP driver

0.3.4

published 0.3.4 • 10 years ago

Changelog

0.3.4 / 2014-05-08

Don't hold memory-leaking references to I/O buffers after they have been parsed

0.3.3

published 0.3.3 • 10 years ago

Changelog

0.3.3 / 2014-04-24

Correct the draft-76 status line reason phrase

Previous 13 Next