doesn't work out of the box with socket.io 1

[portokallidis]

.configure has been deprecated , you have to pass a json obj upon creation.
var socketio = require('socket.io')({'store': store }).listen(3000);

cannot make to work:
WebSocket connection to 'ws://127.0.0.1:3000/socket.io/?EIO=2&transport=websocket&sid=S6wsEH4nJpAMpGTNAAAA' failed: Connection closed before receiving a handshake response

Can you suggest something else?

[fent]

Does it show that without using socket.io-clusterhub?

[portokallidis]

I am using your guide on the front page. i require the module into store variable and then use it.

[portokallidis]

it seems that i closed the issue by mistake. So is this module able to scale socket.io + nodejs apps?? because this would be immensely awesome

[fent]

Yes my usage guide and examples are outdated. But I was wondering if the
error happens without using the module too.

I'll update the readme in a bit.

On Saturday, August 16, 2014, Nick Portokallidis [email protected]
wrote:

Reopened #6 #6.

—
Reply to this email directly or view it on GitHub
#6 (comment).

Roly Fentanes

[fent]

It looks like this part of the socket.io api is deprecated? There is no store option on it anymore. And the error you saw happens when using cluster, regardless of using this module.

socketio/socket.io#1244
socketio/socket.io#1636

[fent]

Yes, it looks like socket.io 1.0 isn't supporting stores anymore, leaving
it up to the programmer to handle keeping track of client data. Therefore
I'll close this for now and add a note in the readme.

On Sun, Aug 17, 2014 at 5:32 AM, Nick Portokallidis <
[email protected]> wrote:

Oh so that's why i couldn't use their redis guide too. it is outdated too.
i'll make an issue on the socket.io repo , thanks for the help!

—
Reply to this email directly or view it on GitHub
#6 (comment)
.

Roly Fentanes