Allow TAP to broadcast item persistence

Dustin, would it be hard to add the capability to TAP to send a "persisted" message when an item is actually written? Then they could hook up an external consumer to only keep the keys/values that have hit the system but not yet been persisted in some off-node system?

It's certainly possible. We have some rigging for observation for the sync on persist code. I'm sure we could extend that to a general "broadcast" type observer that a tap stream could grab. An interesting twist on sync on persist.