Skip to content

Websocket refresh #243

@Corantin

Description

@Corantin

Right now we use interval pulling when we need some data to refresh, couple of problems with that :

  • Poor performance
  • More network usage
  • Pulling is triggered only on current user actions (not other that might just add funds to a Quest)
    Implement a web socket to refresh some data on-demand :
  • New quest should be put on top of the list after being created
  • New claims and claims state update
  • Quest Bounty update

Metadata

Metadata

Assignees

No one assigned

    Labels

    App 📱User-facing issuesenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions