Skip to content

Eventually consistent global state #19

@JAremko

Description

@JAremko

I'm thinking it can be useful if there was a way to create some kind of shared object between all peers and a mechanism to synchronize it.

For example, a bloom filter with an expiration date(while the previous one is valid (not expired) system tries to build the next one.) that stores IDs of all online users. This way we can know in advance if some peer is unavailable.

Removed nonsense

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions