Streaming/in-process dispatch #2
Description
Currently, ESDF assumes that event (commit) dispatch to a Publisher only occurs via a Streamer - a component which reads (tails) the database and pushes new commits out. Event Sinks should also be allowed to perform in-process dispatching immediately after the sink operation, while tracking publish status (via an "unpublished" list or a special tag in the commit entry itself) and updating it.
A recovery procedure would also need to be devised in case a sink crashes to reduce the likelihood of duplicate / out-of-order dispatch. This could be problematic because multiple sink instances may be at work at any given time and the application's state may move on, despite the earlier events not having been published properly.