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.

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

Storage service #12

Open
kovasb opened this issue Dec 25, 2012 · 0 comments
Open

Storage service #12

kovasb opened this issue Dec 25, 2012 · 0 comments

Comments

@kovasb
Copy link
Owner

kovasb commented Dec 25, 2012

  1. Large results should not be stored in datomic directly.
  2. Some kinds of results are not values and can't be stored anyway
  3. Conveying results to other services is easier by using a storage service, rather than asking the consumers to deal with datomic.

Therefore

  1. Persisting values should be a secondary step after generating them. This can be a UI gesture.
    1b. What gets stored in datomic should only be a summary or representation of the result, sufficient for a human to see, understand, and take action on.
  2. Must distinguish between persistent values, and results that are only available in the memory of the evaluator.
  3. Need a concept of a storage service, and operations to transparently deal with values that may live in storage
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant