node-websocket-server Google Group

Re: Websocket error in windows during installation

mich...@brandedcode.com (Micheil Smith) — Mon, 16 Apr 2012 19:18:15 UT

Hi,
This module is not known to work on windows and will not likely work on
windows. It has not been updated in the last few months, and as such, I
would suggest that you use one of the other available websocket modules.
Kind Regards,
Micheil

Websocket error in windows during installation

faabdullah.ta...@gmail.com (abdullah tariq) — Mon, 16 Apr 2012 19:13:29 UT

im trying to install websocket server on my windows 7 from my command
prompt using npm.
after giving this command
npm install websoc...@1.0.3

i got error of http 304

kindly Help me out!!

Steady state performance

rgillan...@gmail.com (robg) — Mon, 24 Oct 2011 06:12:05 UT

Micheil,

We're running a whole bunch of performance tests at the moment and was
wondering if you have seen the following. We have a simple server
looping back messages to the client. We timestamp out and in, and use
that to calculate latency. We have one client generate 5000 messages
(in sequence) and measure the response. Offer rate is about 22-25

Re: [node-websocket-server] Re: When will v2.0.0 be out?

mich...@brandedcode.com (Micheil Smith) — Tue, 18 Oct 2011 10:54:54 UT

Hi Joseph,
I'm glad we're at some point of understanding, this is exactly why the group
discussing the design of node-websocket-protocol is currently by invite only
of other members, as to only get the best people working on it and contributing
to it, rather than having these sort of discussions every few weeks.

Re: [node-websocket-server] Re: When will v2.0.0 be out?

jose...@gmail.com (Joseph Gentle) — Tue, 18 Oct 2011 10:12:21 UT

I have no interest in bikeshedding the websocket protocol. I wasn't
trying to complain about it, I was commiserating. I haven't expressed
my tone properly and I've rubbed you the wrong way. I never intended
the offense that you've found in my messages. I'm sorry - I should
have been more explicit about my tone. I know you talked to the

Re: [node-websocket-server] Re: When will v2.0.0 be out?

mich...@brandedcode.com (Micheil Smith) — Tue, 18 Oct 2011 07:59:47 UT

As for the protocol changes, I'm not even going to bother discussing them, go complain on the IETF Hybi mailing list, they'll tell you where to go pretty damn quickly, believe me.
If you do something, then you do it right, if you're going to do something half-assed you may as well not do it at all.
Also, if you'd read one of my previous emails, that stated that I already had the support of the socket.io and Faye authors, who I will be bouncing ideas off quite frequently in the coming months. For now Owen of SocketStream and Julien (hopefully I've spelt his name right) from Superfeedr get most of my rough ideas bounced of them. There is a reason I'm doing the project this way, and I'm allowed to as its my project, feel free to fork it if you want, but you'd be taking on a task you probably don't want to take on.

Re: [node-websocket-server] Re: When will v2.0.0 be out?

jose...@gmail.com (Joseph Gentle) — Tue, 18 Oct 2011 02:54:14 UT

They really have added an awful lot of shit into that protocol.
- Do people want partial frames? That only sounds useful for doing
something like file upload via websockets, which sounds like a
terrible idea anyway.
- Extensions need browser support, right? So, will anyone actually use them?
- Fragmented frames don't sound useful to any of the projects you've

Re: When will v2.0.0 be out?

mich...@brandedcode.com (Micheil Smith) — Tue, 18 Oct 2011 01:48:06 UT

Okay, so let's see..

Where's support for:
- fragmented frames
- ping/pong
- binary messages
- close code + reason sending
- close code + reason receiving
- extensions
- and a bunch more I won't detail here, but you can refer to the
various drafts for.

Essentially, yes, you can look at the protocol and think it is simple

Re: [node-websocket-server] Re: When will v2.0.0 be out?

jose...@gmail.com (Joseph Gentle) — Tue, 18 Oct 2011 01:18:32 UT

I've been working on a nodejs browserchannel implementation which I'd
like to add websockets to eventually. I was tempted to just fork out
socket.io's websocket server code into a separate project and use
that.
To be honest, figuring out a decent enough API for websockets doesn't
sound that hard. It'll be a pretty basic API, and we can iterate on it

Re: When will v2.0.0 be out?

mich...@brandedcode.com (Micheil Smith) — Tue, 18 Oct 2011 00:44:51 UT

The conversation on node-websocket-protocol is taking place mainly on
the
node-websocket-protocol mailing list [1], but also via chat and in
person when
I met various people in person. You will need to request to join that
mailing list,
as I'm wanting to keep it to just a small group that definitely will

Re: When will v2.0.0 be out?

jose...@gmail.com (Joseph Gentle) — Tue, 18 Oct 2011 00:30:52 UT

Thanks Micheil.
Where is that conversation taking place? I would be interested to see the
progress.
-J

Re: When will v2.0.0 be out?

mich...@brandedcode.com (Micheil Smith) — Mon, 17 Oct 2011 16:56:16 UT

Hi all,

At present node-websocket-server progress is blocked pending the
design of the API of node-websocket-protocol, which is a collaborative
community effort. I will hopefully be getting some time to put
together a formal proposal for it's API design over the next few days.

Version 2.0.00 of node-websocket-server will likely have a completely

Re: When will v2.0.0 be out?

mich...@brandedcode.com (Micheil Smith) — Tue, 13 Sep 2011 09:40:38 UT

At present there is no release timeline, as while the work on node-
websocket-server itself is relatively small, the work required for
node-websocket-protocol (a generic websocket protocol implementation
for node.js) is a lot larger. We're currently trying to work out the
best API for this project, which means that node-websocket-server must

When will v2.0.0 be out?

instc...@gmail.com (Khoa Nguyen) — Tue, 13 Sep 2011 05:16:09 UT

Hi miksago,
I'm using node-websocket-server for my current project but it is currently
broken with the recent beta updates of Chrome & Firefox. Do you plan to
develop this further to support draft 7-8-9-10? I'm asking this because I
didn't see much development recently and it seems that you are focusing on

Re: server close or disconnect are not firing

vic....@gmx.com (netSQL) — Sun, 11 Sep 2011 00:10:26 UT

ok, got it working!
solution:
connection.addListener('close' , function(connection)
{ console.log(this.id)});

You should be able to get in gamina v:0.4.x in next few weeks.

Vic