Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Re^2: PSGI, Plack, Twiggy, AnyEvent and SockJS... I need help

by xtpu2 (Acolyte)
on Apr 09, 2014 at 02:38 UTC ( #1081597=note: print w/replies, xml ) Need Help??

in reply to Re: PSGI, Plack, Twiggy, AnyEvent and SockJS... I need help
in thread PSGI, Plack, Twiggy, AnyEvent and SockJS... I need help

Thanks for those tips! I have modified the code accordingly and modified the OP. Unfortunately, the behavior of my code is the same (while your code snippet works correctly).

  • Comment on Re^2: PSGI, Plack, Twiggy, AnyEvent and SockJS... I need help

Replies are listed 'Best First'.
Re^3: PSGI, Plack, Twiggy, AnyEvent and SockJS... I need help
by andal (Hermit) on Apr 09, 2014 at 07:40 UTC

    I guess, the module you create is already called from some event-driven system. In other words, your module is a "callback". The "callback" can't run it's own event distribution. You can register one more "callback" with the main system and then simply return control to the caller. The main system is then responsible for activating your new callback at appropriate time.

    The AnyEvent module is event-distribution system. When you call $w->recv you activate this system, which blocks the main one, which in turn might trigger some time-out for killing your callback. Figure out how to add timers to the main framework. I don't know Plack and don't have any desire to study it, so I can't help you with this, sorry.

    At the core, event-driven programming is very simple. The main part is manager looping over all possible events. When event is encountered, the manager checks if there are any "callbacks" waiting for this event. Those callbacks are activated and the looping continues. The callbacks must finish their work quickly and if necessary, they can register more callbacks for different events.

    Everything else, is specific ways, how different managers keep track of callbacks and events.

      At least from looking at the SockJS documentation, it is based on ( or compatible with) AnyEvent.

      Wow, I think you've nailed it! After reading your post, I started digging into that and came across this, discussing this exact issue:

      I'm posting the modified code here so as not to make the OP confusing. The new code no longer closes the connection immediately, but the timer, for some reason only fires ONCE (the first time), whereas I would like it to keep going. I'm guessing this has something to do with the line undef $w; but when I get rid of it, the timer doesn't fire at all.

      #!/usr/bin/perl use strict; use warnings; use Plack::Builder; use SockJS; use AnyEvent; builder { mount '/echo' => SockJS->new( handler => sub { my ($session) = @_; $session->on( 'data' => sub { my $session = shift; $session->write('got your message'); } ); $session->write('connected'); my $w_cond = AnyEvent->condvar; $w_cond->cb( sub { warn $_[0]->recv } ); my $w; $w = AnyEvent->timer( after => 0, interval => 5, cb => sub { undef $w; # cleanup $session->write('5 seconds have passed'); $w_cond->send(); } ); }; ); };

        You need to mention the timer variable $w inside the subroutine to keep it alive.

        Either move it into a global variable or just mention it in the subroutine so it closes over the value. Even better would be to clean up the timer based on some condition.