*pour brain, mix thoroughly*

Wow, what a morning. Waiting outside in the WAY BELOW freezing cold for 45 minutes and still no bus. *wrap hands around tea mug to restore circulation* Guess I'm working from home today.

Anyways, as I was laying in bed last night thinking "What exactly am I working on tomorrow?", it occured to me that that was the entire reason I started this blog. So, what I've been working on in January:

• Storage API normalization in the "newguts" branch. All storage engines must now (and do!) implement remove, remove_multiple, and remove_all (with an optional callback argument that is called with the messages removed). Also in newguts, the fixed callbacks are made via set_callback(name, cb) and call_back(name, args). This cleans up the code in a couple of places, but eventually I think I'd like to move to passing explicit continuations. It'll make things less tightly coupled. That may or may not happen in this branch.
• Topics. They're in and merged into David's mainline.
• POE::Filter::Stomp is into David's mainline. Both it and topics have been stress tested, and stress tests added for topics and binary images.

I'm sure I'm missing some things, but that's what I get for not updating this blog like I'm supposed to. Anyways, to the more important issue of what I am now working on (note: it's a bad sign when I start making todo textfiles and scattering them around my code directories).

• The __DIE__ handler should fire off an email. This is what I'll be implementing today.
• Callback changes need to be either rewritten as explicitly passed continuations (I'm leaning this way) or documented better. (Note: current call_back implentation relies on a hacked up version of PoCo::Generic that the maintainer hasn't accepted a patch for yet...)
  
• Each store should be able to act as either front-store or back-store. This doesn't blow up, but it currently doesn't work. Should wait for the callback changes before trying this again.
• Once those storage changes are solidified, the Big Paradigm Shift needs to happen. That deserves its own post, so...
• Think about some way to notify people when messages can't be stored for some reason. RECEIPT support is mostly in, so maybe...