Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create example data sync clients #52

Open
oskarth opened this issue Jun 18, 2019 · 6 comments
Open

Create example data sync clients #52

oskarth opened this issue Jun 18, 2019 · 6 comments
Assignees

Comments

@oskarth
Copy link
Contributor

oskarth commented Jun 18, 2019

Create example data sync clients that showcases how to use MVDS. Specifics up for debate, however suggestions are:

  1. Absolute minimal 1:1 possible

Then:

  1. Something with more complicated state a la
  1. Something that uses DS with DAG/sequence numbers to establish basic patterns for this. Potentially hinting at mutlipart upload (images!) a la [1/N] [2/64] messages etc.

cc @decanus @cammellos

I suggest we break out the specific data sync clients with specs into separate GH issues, this is more of an umbrella issue to get things started.

@StatusWrike
Copy link

➤ Oskar Thoren commented:

What's a reasonable estimate for this in your view?

@StatusWrike
Copy link

➤ Oskar Thoren commented:

To do a bit later probably, backlog

@decanus
Copy link
Contributor

decanus commented Jun 21, 2019

@oskarth so we can consider the status-console-client at least a minimal data sync client implementation. I would therefore put this far later as a low priority for when we have more things like remote logs, then we can display how a client interacts with both data-sync and the remote log to offer reliability.

@decanus
Copy link
Contributor

decanus commented Jun 21, 2019

https://notes.status.im/TnMMApvlQH2bu911yIStIA?both I've started this document

@decanus
Copy link
Contributor

decanus commented Jul 6, 2019

https://github.com/status-im/dasy Implementation work.

@StatusWrike
Copy link

➤ Oskar Thoren commented:

Not on critical path for v1, that's in DS integration

Decoupling research efforts from v1 critical path

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants