rust-mq
rust-mq copied to clipboard
RustMQ is the MQTT client written on pure Rust.
hello what do you mean no server in readme? you actually mean that this entire crate is just a client? no broker here?  basically, this crate can only provide...
I have a compiler error. I am building on RPi4 4G using the latest RPiOS. Linux raspberrypi 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux Using libssl.so.1.1...
HI, I see that netopt has been updated to use latest openssl. Is it possible to publish it?
Background: I posted a question to stack overflow: http://stackoverflow.com/questions/39210834/do-any-mqtt-clients-actually-reuse-packet-identifiers The packet identifier is required for certain MQTT control packets (http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/csprd02/mqtt-v3.1.1-csprd02.html#_Toc385349761). It's defined by the standard as a 16bit integer (presumably),...
In the codebase the call to `self_disconnect` is commented. Why? This will prevent sending any kind of proper `DISCONNECT` package to the broker. https://github.com/inre/rust-mq/blob/master/mqttc/src/client.rs#L238
https://github.com/inre/rust-mq/blob/master/mqtt3/src/write.rs#L74 Maybe all the writes should be replaced with `write_all` since `write` doesn't guarantee complete writes? This would be problem while doing synchronous request/response since you can't do a `read_incoming_mqtt`...
https://github.com/inre/rust-mq/blob/master/mqtt3/src/read.rs#L155 Hi @inre. Is that correct? Maybe you forgot to do `take(len)`?
Hi, in mqttc-0.1.4/src/client.rs, line 690: ```rust fn _write_packet(&mut self, packet: &Packet) { trace!("{:?}", packet); self.conn.write_packet(&packet).unwrap(); } ``` the `unwrap()` panics: ``` thread 'main' panicked at 'called `Result::unwrap()` on an `Err`...
One use I saw is `PubOpt::new`, whose first arg is Qos. At the moment, I have to add mqtt3 do Cargo.toml, which I would rather avoid (since it's an implicit...
Is it possible to use same client to subscribe (and read incoming messages) and publish at the same time? ``` loop { match client.await().unwrap() { Some(message) => println!("{:?}", message), None...