Home

Yet Another Perl Conference 2006

Per-day:

Monday, Tuesday, and Wednesday.

Or, just the highlights:

Object construction and persistence

Moose - object construction system, it seems like a better way to do what we do with our accessor defs. we will need to do some performance testing though - it was mentioned that Moose is slow, but we don't really know. Moose is based on the Class::MOP code, so if Moose doesn't work out, maybe we can use this to make our accessordef stuff cleaner. Also, it does automated late-loading. That's pretty sweet. Also, it implements Roles, which are like ruby mix-ins.

Data persistence Some exciting stuff seems to be happening in the data persistence area. DBM::Deep holds object hashes literally on disk and does lookup on access. Keeps you from using any memory and give you continuous persistence. This'd be perfect for session if it was backed by memcached, which the author seemed interested in helping me achieve. Presto also, adds find/commit functionality to DBM::Deep.

Why don't we put our validation alongside our model attributes - better protection and more portable validation- no repeated controller code.

Framework ideas

Some additional flexibility in our dispatcher might be good. We tout our "more structured, state-machine-based" navigation model, but there's some very useful stuff we can't do right now. Patrick suggested adding a stack of gatekeepers to each url instead of one pageflow - each gatekeep does a check and loads a particular pageflow if necessary.

Look into using a module to dynamically handle files that don't exist so we don't need empty skeletons.

We should add profiling times into our superclasses when dev mode is on.

Can we unthaw less of a user's session? Just exactly what we need, for instance? This would be nice for a heavily ajax application.

Methodology, research, etc.

Additional things to automate with tests:

Pick ONE debt to pay off/side job to finish. Pick the most important and get it done. There will be a next important.

At some point, we need to clean up our Javascript. We should check out JSAN at that point, to help us manage our JS libraries.

Let us neer consider Mason for anything ever again. I saw two talks on it that failed to move me to anything bug disdain.

Let's do a better job joining the perl community. Perlmonks, some lists, etc.

Things to check out: