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

Write Tutorial For Concurrent Storage #1196

Closed
vaage opened this issue Dec 18, 2017 · 1 comment
Closed

Write Tutorial For Concurrent Storage #1196

vaage opened this issue Dec 18, 2017 · 1 comment
Labels
status: archived Archived and locked; will not be updated status: will not implement The team chooses not to implement this enhancement

Comments

@vaage
Copy link
Contributor

vaage commented Dec 18, 2017

Now that concurrent storage is fixed. We need to write a tutorial showcasing how to use it.
@vaage vaage added the type: docs Improvements or fixes to documentation label Dec 18, 2017
@vaage vaage added this to the v2.4.0 milestone Dec 18, 2017
@vaage vaage self-assigned this Dec 18, 2017
@joeyparrish joeyparrish mentioned this issue Dec 18, 2017
Closed
@joeyparrish joeyparrish modified the milestones: v2.4, v2.5 Mar 4, 2018
@joeyparrish joeyparrish modified the milestones: v2.5, v2.6 Jul 9, 2018
@vaage vaage removed their assignment Mar 5, 2019
@joeyparrish joeyparrish modified the milestones: v2.6, Backlog Feb 12, 2020
@joeyparrish joeyparrish added status: will not implement The team chooses not to implement this enhancement and removed type: docs Improvements or fixes to documentation labels May 1, 2020
@joeyparrish joeyparrish removed this from the Backlog milestone May 1, 2020
@joeyparrish
Copy link
Member

Concurrent Storage does not seem to need a separate tutorial. The store() method can be called multiple times on the same Storage instance now, as one might naturally assume.

@shaka-project shaka-project locked and limited conversation to collaborators Jun 30, 2020
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status: archived Archived and locked; will not be updated status: will not implement The team chooses not to implement this enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@joeyparrish @shaka-bot @vaage