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

Inner Entry types should have proper Value type over String #66

Closed
Firstyear opened this issue Jul 27, 2019 · 0 comments
Closed

Inner Entry types should have proper Value type over String #66

Firstyear opened this issue Jul 27, 2019 · 0 comments
Milestone

Comments

@Firstyear
Copy link
Member

We currently have all attr-values as (String, Vec), however we need to support more complex data types - for example, credentials for IDM will require a complex struct type containing a set of claims, time limits, the credentials themself and more.

However, decoding this from string all the time via b64 cbor would be costly - instead, we should have AVA's support proper "Value" type with an enum, that can return the correct types, and allow encoding more information, doing value-aware operations in replication and more. We can also use this to encode things like CSNs and more.

Finally, this also means we would reduce the need to access schema on compare operations, and we can have more complex indexing outputs IE 1 ava -> many index outputs.

This will be a huge change but it's critical for credential storage and more to support this.

@Firstyear Firstyear added this to the v1 milestone Jul 28, 2019
This was referenced Jul 28, 2019
@Firstyear Firstyear mentioned this issue Aug 14, 2019
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant