Skip to content

Refactor futures, switch to core.async channels #2

@DaniruKun

Description

@DaniruKun

At the moment the app spawns 6+ threads with future and uses atom swaps and derefs for the concurrent control logic. While this approach works, it consumes way too many resources and depends on a single large atom map.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions