decentralized-identity / decentralized-identity/universal-resolver

Caching

Open
#9 2 comments 0 reactions 0 assignees View on GitHub
enhancement reorganize-in-other-issues
Dominant language
Java
Stars
644
Forks
305
Avg merge
5h 11m
Merged PRs (30d)
1

Description

How should resolution results be cached?

This could be influenced by:
- Default settings by community consensus and recommendations of the IND WG.
- Custom configuration by the UR administrator.
- Request parameters by a UR user (e.g. to override defaults and force a fresh non-cached lookup).
- Settings associated with the identifier (e.g. TTL setting in the DID document or BNS zone file).

How should the cache be implemented? The UR could cache results in memory, or use a shared caching mechanism such as Blockstack's [Atlas peer network](https://github.com/blockstack/atlas).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.