Commits on Apr 30, 2015
  1. Version 1.50430 releng

    alexmv committed Apr 30, 2015
  2. Fix a backwards L<> in POD

    alexmv committed Apr 30, 2015
  3. Fix typos found by Debian

    alexmv committed Apr 30, 2015
    Fixes CPAN #75581
  4. Switch to the modern "use utf8"

    alexmv committed Apr 30, 2015
    Fixes CPAN #102760
Commits on Nov 25, 2013
Commits on Aug 19, 2013
  1. Drop Clientside sessions, which have never had any tests to an option…

    obra committed Aug 19, 2013
    …al feature.
    (They depend on CGI::Cookie::Splitter whose tests broke with has randomization and hasn't been touched since 2007)
Commits on Jun 24, 2013
  1. YAML::Syck 1.22 fixed a spelling error in an error message which we c…

    tsibley committed Jun 24, 2013
    As a result, we failed to catch the error and the SetupWizard tests
    failed.  Refer to
    Resolves #86331.
Commits on May 29, 2013
Commits on Feb 19, 2013
  1. Merge branch 'pubsub'

    alexmv committed Feb 19, 2013
Commits on Feb 17, 2013
  1. Remove old dead code from jifty.js

    alexmv committed Nov 5, 2012
    This code should have been removed in cc0a6f0.
Commits on Feb 15, 2013
  1. Unescape and potentially decode UTF8 in REST paramters

    tsibley committed Feb 15, 2013
    The dispatcher doesn't unescape matched URL values.  Without the
    unescaping, it was impossible to use basic REST urls for values
    containing reserved characters.
    A basic test of functionality is included.  The test file fails before
    this commit.
Commits on Nov 5, 2012
  1. Update MANIFEST

    alexmv committed Nov 5, 2012
  2. Intentionally ignore subscriptions during region push

    alexmv committed Nov 5, 2012
    When regions were rendered in response to events, they had the
    opportunity to attempt to add new subscriptions via Jifty->subs->add.
    However, such calls added to the in-memory store for the client_id that
    had already been fetched -- and thus were lost.  Despite this, two
    different pieces of code attempted to manage the region subscriptions
    during event-triggered region rendering.
    Remove the misleading code, and replace it with an explicit mention of
    the missing functionality.
  3. Allow Jifty->subs->add( topic => "..." ) for direct-to-client subs

    alexmv committed Nov 5, 2012
    Previously, the canonical way to subscribe the web browser's bus to
    messages on the message bus was to create a YourApp::Connection class:
        package YourApp::PubSub;
        use base qw/ Jifty::Plugin::PubSub::Connection /;
        sub connect {
            my $self = shift;
            $self->subscribe( qw/ some_event other_event / );
    Also provide a simpler method, for when the subscriptions depend on
    which page is visited, by making use of the existing
    Jifty::Plugin::PubSub::Subscriptions->add method:
        Jifty->subs->add( topic => $_ )
            for qw/ some_event other_event /;
  4. Add a Jifty AnyMQ subclass which pushes "type" explicitly

    alexmv committed Nov 5, 2012
    If a client subscribes to multiple topics, they have no way of
    differentiating which topic a newly-arrived message came from; as a
    convention, Jifty uses the "type" key of the data to store the topic
    that the message was published on.  Provide an AnyMQ subclass to catch
    data which already uses that key, and to provide an interface which
    papers over the call to ->topic().
Commits on Nov 4, 2012