Places, faces

Place needs to be renamed to Destination to be less confusing, and then we need to hunt for where we're using $destination and either convert them to real destination objects (and use $destination->name) or call them $destination_name.

The Valentine's Day File

The following are the MQ issues discussed on 2008-02-14 (herein after
referred to as the "Valentine's Day File"):

* Complex: granularity and timeout
* Race condition: pumping queues
* Clean up cycle
* Non-persistent messages: expel from front-store per normal, remove
when expired during clean-up cycle

non-persistent messages

So I don't forget, we need to look into what guarantees ActiveMQ makes about non-persistent messages and try to do something sane with them. Currently, we just sort of let them fall out of the front store.

Mooooooo...se.

So, the moose branch has everything but statistics all moosed up. Statistics isn't breaking anything, at least, but I don't really want to spend any time mucking with it because I have painted a giant red target on it. I want it to Go Away, which it probably will when I write real monitoring tools. So. But all the core stuff is Moosed, now, and all the callback stuff is chugging right along being happy, so I think it's time to yank myself out of the land of refactoring and into New Feature Territory. Which is more fun anyways.

I went to open up a text file to talk to myself in about clustering, then I remembered this blog. And I read some of my old posts, and I remembered that the Next Thing is the fixed-size stores. This is going to be some changes to Complex more than anything, and will just be changing the way expire works first of all. Need peek() for all stores. Need to remember some data about whether messages have been persisted in Complex, so I can let things all out of the front store if they have. I think peek() first. Then persistence memory. Then expire change. Then backstore-pulling.