You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: