Skip to content

Feature request: way to get sync progress from API #745

Open

Description

@stevedekorte

It would be nice if there were a way to get some rough measure of sync progress via the API. Something like: 1) the number of total cached messages visible on connected nodes and 2) number of cached messages on local node. This way clients could poll it to display sync progress to the user. Otherwise, they think it's broken and see no reason to leave the app open while it syncs.

Activity

  1. added this to the v0.6.0 milestone on Nov 11, 2015
  2. self-assigned this
    on Nov 11, 2015
  3. PeterSurda commented on Nov 11, 2015

    @PeterSurda
    Member

    This sounds interesting.

  4. stevedekorte commented on Nov 11, 2015

    @stevedekorte
    Author

    Right now I just show # of messages processed, which at least let's users see that it's doing something. What I'd really like to show is: "number of messages other nodes have told me about but I don't have yet".

  5. PeterSurda commented on Nov 11, 2015

    @PeterSurda
    Member

    Yes that's how I understood it too. I think it would be helpful to see the progress status and I also think it is doable.

  6. PeterSurda commented on Nov 11, 2015

    @PeterSurda
    Member

    Do you want this shown in the UI, exposed to the API calls or both?

  7. stevedekorte commented on Nov 11, 2015

    @stevedekorte
    Author

    In the API. We've written our own Bitmessage UI app called Bitpost: https://voluntary.net/bitpost/

    We may be doing a JS port next year and moving to the JS implementation of Bitmessage.

  8. added a commit that references this issue on Nov 11, 2015
  9. PeterSurda commented on Nov 12, 2015

    @PeterSurda
    Member

    Look at the latest two commits in my fork (mailchuck@53062f6 and mailchuck@f933cea) for guidelines how to write the API change yourself. The commits expose the number of unsynced objects to the GUI in the network tab. I don't plan on making the API change myself before 0.6, but I can merge a commit if you want to do it.

  10. modified the milestones: v0.8.0, v0.6.0 on Nov 12, 2015
  11. added a commit that references this issue on May 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions