message-io VS tungstenite-rs

message-io: a networking library meant to be very simple, built on mio.

Another one I know about, but have not looked into yet, is message-io.

I'm working in a transport network library that possible fits as a building block for yours and solves the problem of using different underlying transports: message-io

Here is benchmarks

I think https://github.com/lemunozm/message-io can be a good candidate.

The idea behind message-io is not to populate a current transport with a lot of options/profiles/modifications... this obfuscates the default way of working with it. Instead, if you want to build some behaviour on top of it, it is as easy as making an adapter! Following this pattern, you can split the way of using the library from the behaviour of the transport, keeping the things simple.

The initial purpose was to show the capabilities of https://github.com/lemunozm/message-io Nevertheless, Termchat is growing and needs to polish some of its features. At this point it is not for real-world use but I hope to reach this target.

You can start by following tungstenite-rs client example. And since you are connecting to an tls enabled endpoint you should enable tls features. And according to your API's doc it requires you to send serialized json string for requesting message response and you can use serde ande serde_json for serialization. This is a complete example where a hardcode string request:

staticpi, is a websocket forwarding service. Basically, it enables one to keep a Raspberry pi, or any computer, “connected”, in order to send and receive messages to and from any client, without having to deal with a static IP address, open ports on your router, or similar. Built in Rust, using axum, which in turn uses tungestine-rs for the websocket connections, tokio, sqlx, redis-rs and others.

There is a client module and client examples. If using tokio, there is tokio-tungstenite on top, which has various client functions.

tungstenite: "Lightweight stream-based WebSocket implementation. It's formerly WS2, the 2nd implementation of WS. WS2 is the chemical formula of tungsten disulfide, the tungstenite mineral."

tungstenite-rs

If you just want to connect to an existing api, async-tungstenite has a connect function. It should work with wss. See some discussion of this issue here.