rodio VS gRPC

I'm currently working on creating a desktop app with web UI using Yew (wasm32-unknown-unknown), and Tauri for the desktop packaging side of things. In this particular case, I'd like to be able to play audio files from the user's local filesystem using the rodio crate, and also to process text files for purposes such as configuration, for example by using the csv crate. I know for absolute certain that the app will only be run in a desktop context, i.e, Windows, Linux and MacOS, and therefore will always have a filesystem physically existent despite any WASM sandboxing (which I'm aware of, hence asking for any possible methods).

I'm currently working on creating a desktop app with web UI using Yew, and Tauri for the desktop packaging side of things. In this particular case, I'd like to be able to play audio files from the user's local filesystem using the rodio crate, and also to process text files for purposes such as configuration, for example by using the csv. I know for absolute certain that the app will only be run in a desktop context, i.e, Window, Linux and MacOS, and therefore will always have a filesystem physically existent despite any WASM sandboxing (which I'm aware of, hence asking for any possible methods).

There's symphonia for audio, although it's quite low-level. rodio is a better choice if you just want to play some sounds.

The Music Player is based on Rodio, which is a high-performance audio playback library for Rust, and Symphonia, which is a Rust library for working with music metadata and audio decoding. This allows the Music Player to provide high-quality audio playback and management.

https://crates.io/crates/rodio Its based on cpal and has basic necessities like resampler.

I believe rodio is generally regarded as a good spot to start for audio in Rust. Open Game Art has a fair few tilesets, you could take a look there.

I have tried the https://crates.io/crates/rodio crate already but I did not find a way to change the parameters while the background thread is playing the song.

I changed into mp3 cuz I didn't know how to use rodio to play other file format like m4a, because it needed symphonia and I could'nt find any example of symphonia on the internet.

Also, you can now use Symphonia as a backend in rodio.

gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle.

Yes, grpc_cli tool uses essentially the same mechanism except implemented as a grpc service rather than as a stubby service. The basic principle of both is implementing the C++ proto library's DescriptorDatabase interface with cached recursive queries of (usually) the server's compiled in FileDescriptorProtos.

See also https://github.com/grpc/grpc/blob/master/doc/server-reflecti...

The primary difference between what grpc does and what stubby does is that grpc uses a stream to ensure that the reflection requests all go to the same server to avoid incompatible version skew and duplicate proto transmissions. With that said, in practice version skew is rarely a problem for grpc_cli style "issue a single RPC" usecases: even if requests do go to two or more different versions of a binary that might have incompatible proto graphs, it is very common for the request and response and RPC to all be in the same proto file so you only need to make one RPC in the first place unless you're using an extension mechanism like proto2 extensions or google.protobuf.Any.

While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future.

The loadBalancingConfig is what we use in order to decide which policy to go for (round_robin in this case). This JSON representation is based on a protobuf message, then why does the name resolver returns it in the JSON format? The main reason is that loadBalancingConfig is a oneof field inside the proto message and so it can not contain values unknown to the gRPC if used in the proto format. The JSON representation does not have this requirement so we can use a custom loadBalancingConfig .

The Dart implementation of gRPC which puts mobile and HTTP/2 first. It's built and maintained by the Dart team. gRPC is a high-performance RPC (remote procedure call) framework that is optimized for efficient data transfer.

gRPC is a high-performance, open-source RPC (Remote Procedure Call) framework initially developed by Google. It uses Protocol Buffers for serialization and supports bidirectional streaming.

In general, tunneling through HTTP2 turns out to be a great choice. There is a RPC protocol built on top of HTTP2: gRPC[1].

This is because HTTP2 is great at exploiting a TCP connection to transmit and receive multiple data structures concurrently - multiplexing.

There may not be a reason to use HTTP3 however, as QUIC already provides multiplexing.

I expect that in the future most communications will be over encrypted HTTP2 and QUIC simply because middleware creators can not resist to discriminate.

[1] <https://grpc.io>

Even in the https://grpc.io blog says this

gRPC