- Rust 99.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
77acd92c62
From the prosody@ room: - 0114 doesn't mention the removal of @version on the stream, and it refers to 3920 which has it as a MUST. - 0114 streams have historically never used @version="1.0" - @version="1.0" implies stream features which 0114 doesn't have. - There was a proposal years ago to fix this but a new XEP was preferred (0225). The change here uses a compile-time check, and may have to change when support for 0225 arrives if it's still gated behind the "component" feature (even though it may be weird to have both under the same feature). We'll see when we get there. Signed-off-by: pep <pep@bouah.net> |
||
| .forgejo/workflows | ||
| jid | ||
| minidom | ||
| parsers | ||
| sasl | ||
| tokio-xmpp | ||
| xmpp | ||
| xso | ||
| xso-proc | ||
| .gitea | ||
| .github | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| Cargo.toml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| typos.toml | ||
xmpp-rs
What's this?
A set of rust XMPP libraries with the goals of being type-safe and well-tested.
xmppprovides a high-level API for the protocol. You shouldn't need to know about the protocol to use it. Still very much WIP.tokio-xmppis a lower-level library that handles the XMPP stream(s).xmpp-parsersparses XML into Rust and back.minidomis a DOM library quite specific for XMPP.jidis a Jid parsing library.saslhandles the SASL protocol.xsoandxso-procprovide the procedural macros poweringxmpp-parsers.
Community
There is an XMPP MUC for the discussion of these libraries, feel free to join! :)
A Code of Conduct is available as CODE_OF_CONDUCT.md in the repository for the well-being of the community. Please refer to it in case of a possible conflict in any of the xmpp-rs venues (channel, forge, etc.).
Contributing
Thank you for your interest in the project!
Contributing rules are available as CONTRIBUTING.md in the repository.
License
Mozilla Public License 2 (MPL2). See the LICENSE file.
Building
Dependencies should be provided by crates if you use the default features. If
you use tokio-xmpp's tls-native feature you will need an ssl library
(openssl, libressl, etc.).
cargo build
The various features available should be explained in the crates themselves.