Websocket inside rust to update state

[decipher3114]

Is there any example showing the usage of websocket in rust that constantly update the UI. The websocket is expected to receive about 10 msgs per sec. Will that cause an issue with the structure??

[temeddix]

Hi, using websocket crates should work nicely with Rinf, in async Rust code. As introduced in the Rinf docs(link), if you choose to use the actor model, and pass messages received from the websocket to an actor, storing the latest data you received from the websocket is possible. Or you can directly pass Protobuf messages converted from websocket messages to Flutter widgets, too.

I personally recommend using async_tungstenite or tokio_tungstenite for this.

Unfortunately there isn't any example for this in the current repository right now.

[decipher3114]

I am actually thinking about shifiting from iced to rinf. Since it is pure rust, it can handle 3 websockets efficiently.

My usecase is not performance critical but time critical. So, do you recommend shifting to it??

Will the protbuf be an issue in this case??

[temeddix]

Since you're sending tens of messages per second, Protobuf won't be an issue. Protobuf is know to be very efficient.

As you said, since Rinf makes you write the logic in pure Rust, complex business logic can run efficiently in an async runtime like tokio. Using Rinf for an application that heavily relies on websocket is what I'm actually doing in my personal projects. In my case, there are 4 websockets, each handling tens of thousands of messages per second(though not all of them are rendered on the UI).

I haven't used iced before, but I can say that Rinf does work well with this purpose.

[decipher3114]

@temeddix I am having certain issues due to my aquantaince with iced.

Do you have any app that have multiple messages and a central state to manage? The example seems very lacking. I am using messages crate as shown in the example. But state doesn't contain any field.

I also don't know if I should send the whole state as update to the UI or a certain part of it.