The example provided with this module failed about sockjs-perl

[vti]

Yes, this is a problem with Twiggy. See Issue #1

[akarelas]

I just installed your master version of Twiggy. Should that fix the problem? (I can't check just yet, have to install everything else, too)

[vti]

Yes, that should work. I use myself. I think... :)

[akarelas]

Why not mention in the README.md that your own Twiggy is required?

That way this here issue will be un-needed.

[vti]

On 03/06/2013 05:26 PM, Alexander Karelas wrote:

Why not mention in the README.md that your own Twiggy is required?

That way this here issue will be un-needed.

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

Yes. I am going to add that.

[akarelas]

Is "$stringifying" the session object the only way to get a unique id out of it?

[vti]

What do you need it for?
09.03.2013 7:23 ÐÏÌØÚÏ×ÁÔÅÌØ "Alexander Karelas" [email protected]
ÎÁÐÉÓÁÌ:

Is "$stringifying" the session object the only way to get a unique id out
of it?

Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-14658354
.

[akarelas]

I will need to keep track of which clients are in each room (to emulate the rooms functionality from socket.io). Also which rooms each client is in. This requires at least two hashes with unique ids as keys.

[akarelas]

Also, is there a future-proof way to hook a new subroutine on the "user closed his connection" event?

I was thinking of replacing $socket->{"on_aborted"} with a subroutine that first executes what was there before, and then executes my own code. Does that seem right?

[akarelas]

For some reason, "on_aborted" is executed twice on browser-reload.

[vti]

Maybe providing a way for either subclassing and/or setting custom variables for the session object would be a good idea. This way you could save your own unique ids, and overwrite events.

As for "executed twice" this could a bug.

[vti]

Ok, now you can set/get custom values by using:

$session->set(foo => 'bar');
$session->get('foo');

And overwrite session creation by providing you own factory:

SockJS->new(session_factory => sub { MySessionClass->new })

[akarelas]

Both changes worked very well. Thank you.

[rsarvas]

Thanks, that helps. The demo still fails using FireFox 12 and 23 (makes initial contact, but aborts during the xhr post). IE 9 also appears to fail (xhr issues again?). On the plus side, the example code works fine now using web sockets in the latest version of Chrome.

I'm going to check the Perl module dependencies on my end again, then try to pull down the latest copy of the sockjs (JavaScript) library just to make sure this isn't a client or configuration issue.