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.

Sign up for GitHub

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

Jump to bottom

implement general flow for async callbacks, optimistic updates and offline mode #9

Closed
0xgeert opened this issue May 22, 2014 · 2 comments
Closed

implement general flow for async callbacks, optimistic updates and offline mode #9

0xgeert opened this issue May 22, 2014 · 2 comments

Comments

@0xgeert
Copy link
Owner

0xgeert commented May 22, 2014

http://stackoverflow.com/questions/23635964/how-do-you-manage-asynchronous-store-operations-with-flux
@0xgeert 0xgeert mentioned this issue May 22, 2014
Closed
2 tasks
@0xgeert
Copy link
Owner Author

0xgeert commented May 27, 2014

offline processing (with say #7 puchdb) would be simply the optimistic route. Ideally, we would have validation be done on the client as well, so only partitioning/ network failure would result in optimistic ok followed by server side fail.

@0xgeert
Copy link
Owner Author

0xgeert commented May 30, 2014

validation extracted from this issue to #18 (Dry clientside validation)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@0xgeert