Walter Bonetti

Hi folks, The same need here, Is there a way to workaround temporarily. I'd to use this crate for a project. But, I must comply with m2m without a DNS...

Hi @hawkw, I updated the issue with your summary. Thank you by the way. The search engine didn't come with #858 . I will look into it. No time for...

@mattfbacon I have a lot of intereset in this feature. I would like to use it with NGINX over Unix domain.

Related https://github.com/SergioBenitez/Rocket/discussions/2110.

@de-sh, how much work do you estimate it? Is it as straightforward as the transport layer in the mqttc? If so, I'd like to figure out a solution to allow...

Should we use the field listen from rumqttd.conf to determine the selected transport layer? - e.g `ws://ip:port` and `wss://ip:port` Should we break the configuration file and use `url` crate? -...

Based on the work of rumqttc, I tried to reuse the WsStream from tungstenite. But, It does not implement Sync yet. I opened an issue https://github.com/najamelan/ws_stream_tungstenite/issues/8. #### Edit: Another question...

@de-sh, Unless I'm doing it wrong, the support of MQTT over WebSocket should be like that? ```rust match self.config.listen.scheme() { #[cfg(feature = "websocket")] "ws" | "wss" => { // ......

The `url` crate provide a serde interfaces. `listen: Url` parses the `listen` field and provides `scheme()`. The scheme for `ws://ip:port` is `ws`. For the current state of the art, it...

We should consider `url` crate or a custom crate. See what is happening with https://github.com/bytebeamio/rumqtt/pull/193 and https://github.com/bytebeamio/rumqtt/issues/270. Edit: - My proof of concept can be find here: https://github.com/IniterWorker/rumqtt/tree/feature/websocket