593b5e55cb
This removes a massive performance issue since getting sessions is part of every message send cycle. Namely every time we check that all our devices inside a certain room have established 1 to 1 Olm sessions we load the account from the store. This means we go through an account unpickling phase which contains AES decryption every time we load sessions. Cache instead the account info that we're going to attach to sessions when we initially save or load the account. |
||
|---|---|---|
| .github/workflows | ||
| contrib/mitmproxy | ||
| matrix_sdk | ||
| matrix_sdk_base | ||
| matrix_sdk_common | ||
| matrix_sdk_crypto | ||
| matrix_sdk_test | ||
| matrix_sdk_test_macros | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| Cargo.toml | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| tarpaulin.toml | ||
README.md
matrix-rust-sdk
matrix-rust-sdk is an implementation of a Matrix client-server library in Rust.
Project structure
The rust-sdk consists of multiple crates that can be picked at your convenience:
- matrix-sdk - High level client library, with batteries included, you're most likely interested in this.
- matrix-sdk-base - No (network) IO client state machine that can be used to embed a Matrix client in your project or build a full fledged network enabled client lib on top of it.
- matrix-sdk-crypto - No (network) IO encryption state machine that can be used to add Matrix E2EE support to your client or client library.
Status
The library is in an alpha state, things that are implemented generally work but the API will change in breaking ways.
If you are interested in using the matrix-sdk now is the time to try it out and provide feedback.