-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
➤ Oskar Thoren commented: What's a reasonable estimate for this in your view? |
➤ Oskar Thoren commented: To do a bit later probably, backlog |
@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. |
https://notes.status.im/TnMMApvlQH2bu911yIStIA?both I've started this document |
https://github.com/status-im/dasy Implementation work. |
➤ Oskar Thoren commented: Not on critical path for v1, that's in DS integration Decoupling research efforts from v1 critical path |
Create example data sync clients that showcases how to use MVDS. Specifics up for debate, however suggestions are:
Then:
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.
The text was updated successfully, but these errors were encountered: