1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166
//! # RSMQ in async Rust //! //! RSMQ port to async rust. RSMQ is a simple redis queue system that works in any //! redis v2.6+. It contains the same methods as the original one //! in [https://github.com/smrchy/rsmq](https://github.com/smrchy/rsmq) //! //! This crate uses async in the implementation. If you want to use it in your sync //! code you can use tokio/async_std "block_on" method. Async was used in order to //! simplify the code and allow 1-to-1 port oft he JS code. //! //! [](https://crates.io/crates/rsmq_async) //! [](https://choosealicense.com/licenses/mit/) //! [](https://deps.rs/crate/rsmq_async) //! [](https://docs.rs/rsmq_async) //! //! ## Example //! //! ```rust,no_run //! //! use rsmq_async::{Rsmq, RsmqError, RsmqConnection}; //! //! # async fn it_works() -> Result<(), RsmqError> { //! let mut rsmq = Rsmq::new(Default::default()).await?; //! //! let message = rsmq.receive_message::<String>("myqueue", None).await?; //! //! if let Some(message) = message { //! rsmq.delete_message("myqueue", &message.id).await?; //! } //! //! # Ok(()) //! # } //! //! ``` //! //! Main object documentation are in: <a href="struct.Rsmq.html">Rsmq</a> and //! <a href="struct.PooledRsmq.html">PooledRsmq</a> and they both implement the trait //! <a href="trait.RsmqConnection.html">RsmqConnection</a> where you can see all the RSMQ //! methods. Make sure you always import the trait <a href="trait.RsmqConnection.html">RsmqConnection</a>. //! //! ## Installation //! //! Check [https://crates.io/crates/rsmq_async](https://crates.io/crates/rsmq_async) //! //! //! ## Example //! //! ```rust,no_run //! use rsmq_async::{Rsmq, RsmqConnection}; //! //! async fn it_works() { //! let mut rsmq = Rsmq::new(Default::default()) //! .await //! .expect("connection failed"); //! //! rsmq.create_queue("myqueue", None, None, None) //! .await //! .expect("failed to create queue"); //! //! rsmq.send_message("myqueue", "testmessage", None) //! .await //! .expect("failed to send message"); //! //! let message = rsmq //! .receive_message::<String>("myqueue", None) //! .await //! .expect("cannot receive message"); //! //! if let Some(message) = message { //! rsmq.delete_message("myqueue", &message.id).await; //! } //! } //! //! ``` //! //! ## Realtime //! //! When [initializing](#initialize) RSMQ you can enable the realtime PUBLISH for //! new messages. On every new message that gets sent to RSQM via `sendMessage` a //! Redis PUBLISH will be issued to `{rsmq.ns}:rt:{qname}`. So, you can subscribe //! to it using redis-rs library directly. //! //! ### How to use the realtime option //! //! Besides the PUBLISH when a new message is sent to RSMQ nothing else will happen. //! Your app could use the Redis SUBSCRIBE command to be notified of new messages //! and issue a `receiveMessage` then. However make sure not to listen with multiple //! workers for new messages with SUBSCRIBE to prevent multiple simultaneous //! `receiveMessage` calls. //! //! ## Guarantees //! //! If you want to implement "at least one delivery" guarantee, you need to receive //! the messages using "receive_message" and then, once the message is successfully //! processed, delete it with "delete_message". //! //! ## Connection Pool //! //! If you want to use a connection pool, just use <a href="struct.PooledRsmq.html">PooledRsmq</a> //! instad of Rsmq. It implements the RsmqConnection trait as the normal Rsmq. //! //! If you want to accept any of both implementation, just accept the trait //! <a href="trait.RsmqConnection.html">RsmqConnection</a> //! //! ## Executor compatibility //! //! Since version 0.16 [where this pull request was merged](https://github.com/mitsuhiko/redis-rs/issues/280) //! redis-rs dependency supports tokio and async_std executors. By default it will //! guess what you are using when creating the connection. You can check //! [redis-rs](https://github.com/mitsuhiko/redis-rs/blob/master/Cargo.toml) `Cargo.tolm` for //! the flags `async-std-comp` and `tokio-comp` in order to choose one or the other. If you don't select //! any it should be able to automatically choose the correct one. //! //! ## Response types //! //! There are 3 functions that take generic types: //! //! - `pop_message` and `receive_message`: Where the type for the received message is //! `RsmqMessage<E>` where `E: TryFrom<RedisBytes, Error = Vec<u8>>`. So, If you have custom type, you can implement the trait //! `TryFrom<RedisBytes>` for `YourCustomType` and use it like: `rsmq.receive_message::<YourCustomType>("myqueue", None)`. //! Implementations are provided for `String` and `Vec<u8>`. //! - `send_message` where the message to send needs to implement `Into<RedisBytes> + Send`. So you will //! need to implement the trait for your type. You can check the implementations for the type RedisBytes and see how //! we did it. Implementations are provided for `String`, `&str` and `Vec<u8>`. //! //! All this is because strings in Rust are very convenient to use for json messages, so always returning a Vec<u8> //! may not be the most ergonomic solution. But at the same time, we can just add some already made implementations //! for it and you can just use it with your type or, if you are sending, let's say, images, just use the method //! like: `rsmq.receive_message::<Vec<u8>>("myqueue", None)` and transform it later to your type. (Or just implement //! the TryFrom<RedisBytes> for your type and the transformation will be automatic.) //! //! ### Example for implementing a custom type //! //! ```rust,ignore //! impl TryFrom<RedisBytes> for String { //! //! // We sacrifice the ability of recovering the original error for the ability of having the //! // original data. If you know how to conserver both, let me know! //! //! type Error = Vec<u8>; // Always set Error as Vec<u8>; //! //! fn try_from(bytes: RedisBytes) -> Result<Self, Self::Error> { //! String::from_utf8(bytes.0).map_err(|e| e.into_bytes()) //! } //! } //! ``` //! #![forbid(unsafe_code)] mod error; mod functions; mod normal_facade; mod pooled_facade; mod r#trait; mod types; pub use error::RsmqError; pub use error::RsmqResult; pub use normal_facade::Rsmq; pub use pooled_facade::{PooledRsmq, PoolOptions} ; pub use r#trait::RsmqConnection; pub use types::RedisBytes; pub use types::RsmqMessage; pub use types::RsmqOptions; pub use types::RsmqQueueAttributes;