Generating events

    Jifty->bus->publish( "some_event" => {
        some_key  => "data",
    });

This notifies all subscribers of the "some_event" class with the arbitrary payload specified. See AnyMQ for more details of the backend data bus. The "type" key of the data provided is reserved for internal routing.

Consuming events outside the webserver

    my $listen = Jifty->bus->new_listener;
    $listen->subscribe( Jifty->bus->topic("some_event") );
    $listen->poll( sub {
        my ($data) = @_;
        warn "Got some event with " . $data->{some_key};
    }
    # Loop forever
    AE::cv->recv;

Pushing updated regions to the client

    Jifty->subs->update_on( topic => "some_event" );

Events may trigger arbitrary other region updates, using:

    Jifty->subs->add(
        topic  => "some_event",
        region => "...",
        path   => "...",
        # Any other arguments from Jifty::Form::Element
    );

When a region is rendered because it was triggered by an event, it will be passed the triggering event in an "event" variable.

Running javascript in the client in response to events

    Jifty->subs->add( topic => $_ ) for qw/ some_event other_event /;

Once the browser is subscribed, the events will be made available via the global "pubsub" object in javascript, and can be consumed via "bind":

    jQuery(pubsub).bind("message.some_event", function (event, data) {
        alert(data.some_key);
    }

Sending messages from javascript

    pubsub.send({type: 'something', data: 'here'}});

In order to act on these responses, create a "YourApp::PubSub" which inherits from Jifty::Plugin::PubSub::Connection, and override "receive" in Jifty::Plugin::PubSub::Connection:

    package YourApp::PubSub;
    use base qw/ Jifty::Plugin::PubSub::Connection /;
    sub receive {
        my $self = shift;
        my $msg = shift;
        return 1 if $self->SUPER::receive( $msg );
        warn "Got some message from the client: " . $msg->{data};
        return 1;
    }

Note that, for security reasons, this communication from the web browser is not published to the Jifty event bus (though you may opt to republish them there so manually).

init

new_request

body_end

psgi_app_static

wrap