submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

Hello, I am starting to learn and play around with tokio and multithreaded code. I am now playing around with websockets, I don't quite understand the difference between broadcast and mpsc, and when would you use either, I mean, I am assuming broadcast is intended for multiple clients, but multiple clients were able to connect to my mscp channel, and receive a bit of data (but it was weird and partial). So I don't quite get it.

you are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 2 points 3 weeks ago* (last edited 3 weeks ago)

You don't need to arc-mutex an mpsc. On the sender side, clone the sender as many times as you need and pass it by value (each sender owns a clone). On the receiver side you must have only one (mpsc is multiple producer single consumer) which is owned by the receiver.

If you need multiple producers and multiple consumers I recommend this crate: https://crates.io/crates/async-channel

The same pattern applies. No arc, no mutex, just clone the sender and receiver handles for each producer and consumer respectively.

Don't worry about the cloning, channels are specifically designed to be used this way.

this post was submitted on 11 May 2025

9 points (100.0% liked)

Rust

6958 readers

15 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago

MODERATORS

[email protected]