On Wed, Mar 12, 2014 at 6:30 PM, Gordon Sim <[email protected]> wrote: > The journal obviously already records the enqueues and dequeues, it just > doesn't keep them around. One option might be to have a modified > journal/store that kept the data for longer in some way or moved it into > some other repository before removing it from the journals themselves.
Having something like the linear store move the "used" journal files to some kind of archive instead of deleting them / reusing them sounds similar. The questions is whether the store is flexible enough to contain the details like timestamps or some kind of links to connections which enqueued / dequeued the messages.
