-
Notifications
You must be signed in to change notification settings - Fork 554
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
Per-profile data storage system #14
Labels
Priority: Important
This work item is really important to complete for its milestone, but it can be scoped out.
Z-ibt
Temporary label for Ben to keep track of issues he's triaged.
Comments
This was referenced Aug 2, 2019
This was referenced Aug 2, 2019
NB: This is not blocked on #12 since for the prototype only the proto-based cache store is used for storage, so only that needs to be made per-profile. |
@BenHenning Is this done ? Or can anyone work on this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Priority: Important
This work item is really important to complete for its milestone, but it can be scoped out.
Z-ibt
Temporary label for Ben to keep track of issues he's triaged.
Individual profiles will need to have data associated with them directly. Such data requires a system to organize other file I/O systems based on the current profile that's selected. This system should interop directly with the other I/O systems described above rather than reimplement them. One possible manifestation of this might be a series of providers for the other I/O systems based on profile ID.
Note that this system is not responsible for managing the current profile logged in, though it should be designed with per-profile Takeout/Wipeout in mind.
The text was updated successfully, but these errors were encountered: