talek
talek copied to clipboard
Client catch-up / resynchronization strategy
it would be nice if the latency between a publisher writing a message and a client retrieving it is sufficiently long for the message to fall out of the database that there's a recovery strategy for re-synchronization beyond out-of-band resharing of handle, which is the current behavior.