tokio-xmpp: re-export rustls if using rustls backend
The user may have to call some global rustls functions depending on the exact feature set of rustls enabled. Hence, we have to expose it. Concretely, if the user somehow ends up with more than one rustls backend, they have to configure one of the backends as default backend at startup.
This commit is contained in:
parent
8c7b503f12
commit
78714475b2
2 changed files with 5 additions and 0 deletions
|
|
@ -51,6 +51,9 @@ extern crate alloc;
|
|||
pub use parsers::{jid, minidom};
|
||||
pub use xmpp_parsers as parsers;
|
||||
|
||||
#[cfg(feature = "tls-rust")]
|
||||
pub use tokio_rustls::rustls;
|
||||
|
||||
mod client;
|
||||
#[cfg(feature = "insecure-tcp")]
|
||||
mod component;
|
||||
|
|
|
|||
Loading…
Reference in a new issue