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

Clean up handling of various storage paths #20

Open

GoogleCodeExporter opened this issue Aug 29, 2015 · 0 comments

Labels

auto-migrated Priority-Medium Type-Enhancement

GoogleCodeExporter commented Aug 29, 2015

Handling of storage paths for different platforms is currently a mess. We need 
to support storing the Haggle data store and logs in different locations from 
application data (payload of received data objects). This could be done in a 
much cleaner way than done today, supporting setting and discovering best paths 
dynamically depending on platform and current storage space.

Original issue reported on code.google.com by erik.nor...@gmail.com on 11 Feb 2011 at 3:38

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added auto-migrated Priority-Medium Type-Enhancement labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment