Fork of github.com/matrix-org/matrix-rust-sdk
7cab7cadc9
This modifies the cryptostore and storage logic in two ways: * The cryptostore trait has only one main save method. * The receive_sync method tries to save all the objects in one `save_changes()` call. This means that all the changes a sync makes get commited to the store in one transaction, leaving us in a consistent state. This also means that we can pass the Changes struct the receive sync method collects to our caller if the caller wishes to store the room state and crypto state changes in a single transaction. |
||
---|---|---|
matrix_sdk | ||
matrix_sdk_base | ||
matrix_sdk_common | ||
matrix_sdk_common_macros | ||
matrix_sdk_crypto | ||
matrix_sdk_test | ||
matrix_sdk_test_macros | ||
.gitignore | ||
.pre-commit-config.yaml | ||
.travis.yml | ||
Cargo.toml | ||
design.md | ||
LICENSE | ||
Makefile | ||
README.md | ||
tarpaulin.toml |
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.