* Optimise memory usage when calling /g_m_e * cache more events * refactor handling of device list update pokes * Sigh
|3 months ago|
|api||5 months ago|
|internal||3 months ago|
|inthttp||1 year ago|
|producers||11 months ago|
|storage||7 months ago|
|README.md||1 year ago|
|keyserver.go||8 months ago|
This is an internal component which manages E2E keys from clients. It handles all the Key Management APIs with the exception of
/keys/changes which is handled by Sync API. This component is designed to shard by user ID.
Keys are uploaded and stored in this component, and key changes are emitted to a Kafka topic for downstream components such as Sync API.
PerformUploadKeysstores identity keys and one-time public keys for given user(s).
PerformClaimKeysacquires one-time public keys for given user(s). This may involve outbound federation calls.
QueryKeysreturns identity keys for given user(s). This may involve outbound federation calls. This component may then cache federated identity keys to avoid repeatedly hitting remote servers.
### Endpoint mappings
/keys/changesto consuming from the Kafka topic.