You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The contents of messages in a topic should be re-publishable, to facilitate longer-latency synchronization.
One of the things preventing this at the moment is that re-publication of the same message will use the same buckets, and repeated writes to a fixed location will look odd.
One way to fix this is to include the 'epoch' in the hashed random seed used to determine bucket location. That would allow the same sequence umber within a topic to be republished in a subsequent epoch, because both the location will still appear unlinked, and a new nonce would mean the contents are a different, indistinguishable random.
The text was updated successfully, but these errors were encountered:
The contents of messages in a topic should be re-publishable, to facilitate longer-latency synchronization.
One of the things preventing this at the moment is that re-publication of the same message will use the same buckets, and repeated writes to a fixed location will look odd.
One way to fix this is to include the 'epoch' in the hashed random seed used to determine bucket location. That would allow the same sequence umber within a topic to be republished in a subsequent epoch, because both the location will still appear unlinked, and a new nonce would mean the contents are a different, indistinguishable random.
The text was updated successfully, but these errors were encountered: