Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

nothingmuch (5848)

  (email not shown publicly)
AOL IM: foobargorch (Add Buddy, Send Message)


Journal of nothingmuch (5848)

Saturday May 02, 2009
12:34 PM

Elsewhere, Iron Man

Monday December 19, 2005
04:41 AM

Catalyst Blog

The Catalyst development community now has a blog where you can tune into rants and ideas that are vaguely related to Catalyst.

I guess this means this journal has been superseded ;-)

Monday November 28, 2005
06:29 PM


MighTyV's source code was released today. For those who don't know, MighTyV is a Catalyst application, and the winner of the BBC Backstage competition.

This led me to find a very nice talk about it too.

I think the message I most clearly got from the talk is that Catalyst and Perl are a wonderful platform to work on. The reasons for this are:

  • The slides contained no complaints about dealing with Catalyst issues - I'm assuming that if there were problems they were trivial*. I often hear about Ruby on Rails and Maypole that along with their automagical ease of use they also tend to force you into a "one true way" of doing things, and that if you need to stray from that path you're probably out of luck. I felt this with Maypole about a year and a half ago, but it has never happened to me with Catalyst.
  • Just look at the number of CPAN modules mentioned (HTML::TagCloud, Text::Tags::Parser, Search::ContextGraph, Image::Imlib2, DateTime, JSON, Data::ICal::DateTime and a huge list of Catalyst plugins). The Ruby on Rails video has the phrase "Look at everything I'm not doing" repeated over and over again, with respect to actions automatically mapping to templates, and stuff like that. In my opinion this is the real stuff you should not be doing - you should be writing as little code as possible, and the CPAN helps you achieve this goal.

These two points make me feel very confident that Catalyst is by far the most attractive platform to be working on right now, even if perl doesn't have the nicest syntax, or requires more discipline from the programmer.

* note that one of MighTyV's authors, Leon Brocard also wrote Devel::ebug::HTTP, which is possibly an even more convincing example of Catalyst's flexibility

Sunday November 27, 2005
04:43 PM

New Catalyst authentication plugins

The new Catalyst authentication framework was released today! (note that the link might be broken - cpan mirroring is not behaving well recently... the pause incoming directory contains the files for now. As a last resort try downloading manually from but that requires PAUSE credentials)

This was a long awaited rewrite in the catalyst community. I'm glad to report that it's finally up!

The old plugins confused authorization with authentication, and other things. The details on the why part were posted previously.

The released plugins were Catalyst::Plugin::Authentication, Catalyst::Plugin::Authentication::Store::Htpasswd, Catalyst::Plugin::Authentication::Credential::TypeKey, Catalyst::Plugin::Authorization::Roles and Catalyst::Plugin::Authorization::ACL, with Catalyst::Plugin::Authentication::Store::DBIC expected shortly.

Monday November 21, 2005
07:00 PM

Will code for beer!

We've posted beer bounties for various tentative Catalyst projects...

Please come and see if anything interests you:

06:49 PM

Wanted: testers and greedy users

The new authentication plugins will be released very soon, and e need as much testing is we can get from testers, and as many requests for new stores/credentials from users (coding and documentation help is also gladly accepted). These plugins were rewritten to replace the big, heavily duplicated mess that is the current state of authentication plugins for Catalyst.

The design is very modular. For example, storage and verification are decoupled:

        use Catalyst qw/
                Authentication::Store::Htpasswd /;

or even optional - Catalyst::Plugin::Authentication::Credential::TypeKey can be used in conjunction with a store, or without one.
Moreover, role based access control is entirely separate (Catalyst::Plugin::Authroization::Roles).

The idea idea is to make it very easy to mix and match logic and backends freely, and get integration with session plugins, authorization plugins and so forth for free.

We also have a very exciting plugin which is totally new - Catalyst::Plugin::Authorization::ACL.

All of this is under the Catalyst svn repository - it is not yet released to the CPAN.

As usual, the best place to join is is the catalyst channel on


Tuesday November 15, 2005
11:37 AM

New session plugins for Catalyst

In an effort to improve Catalyst's public relations I decided to write in this journal occasionally. Let's see if I can keep this up.

To start this off I'd like to announce that the rewrite of the session plugins is finished, and they have been released.

These plugins make support for all the session goodness more stable and flexible. They let you easily write state and storage plugins (e.g. cookie state, DBI memcached or fastmmap stores) easily, and then mix and match them without a headache.

In the works is a plugin for more fine grained expiry (each key in the session data can be expired independently), and a massive rewrite of the authentication/authorization plugins (naturally with good integration with sessions), that is getting the same kind of consistency and usability.

If you'd like to help (we mostly need testing), come and join us on the #catalyst on Our development is being done in the Catalyst SVN repository, where you can find our work in progress.