I found out today that there are actually a fair few people using my websocket server, and after talking with those people, I give you 1.3.00, which includes some things that I felt were missing or had been requested.
Changelog:
- Added Connection.broadcast, which sends to all connected clients, except the sending client.
- Renamed Connection._id to Connection.id, to be consistent with the Manager's naming.
- Modified echo-server example to also serve up the client.html by default.
- Added the ability to pass in a http.Server instance into ws.createServer() or new ws.Server() as the second parameter.
- Switched to framing packets with \x00 and \xff instead of \u0000 and \uffff.
- Switched to using Array.isArray for checking if a variable is an array, as it's much cleaner and faster then a typeof check.
- Fixed issue #7 with the dead connections hanging around or a connection being wrongfully deleted.
- Added support for the broken head case, even though this is actually against current spec, it may be changed.
This version can be installed via NPM with:
npm install websocket-server
Or you can get it off github.com: http://github.com/miksago/node-websocket-server/tree/v1.3.00
Yours,
Micheil Smith
--
BrandedCode.com
--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com.
To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
is there a test suite for websockets, beyond browser support: http://html5test.com/
regards
Jonathan Chetwynd
I have plenty of cross-browser reduced testcase experience filing SVG
bugs,
which I find useful for understanding implementations, edge cases,
standards errata etc.
I'm about ready to start on web sockets, and would benefit from any
current examples,
and might even write a few ~:"