tokio-tungstenite VS wasm-pack

I can't help you debug your code if you do not provide it. Have you looked at the example client?

It passed all test of the autobahn testsuite And web-socket-benchmark show about 3x faster then tokio-tungstenite

There are example files in the tokio-tungstenite crate called `autobahn-client.rs` and `autobahn-server.rs`. Why are they called autobahn? I googled and can't understand what autobahn is all about. Is it a websocket pattern? Or some protocol?

I'm using another crate that requires tls, specifically tokio-tungstenite, I'll try your suggestions later today once I get home

Tokio-tungstenite - It looks like in this example, it's spamming the task thread with wakeup calls from all of the active connections. This design choice makes me doubt that this was well written in general.

tokio-tungstenite is the more popular library. In frameworks, offhand Axum supports websockets (docs, example)

If you only have one task sending data to the sink, you probably don't need forward, as you can just write to the sink directly (you might not even need to split the stream in the first place, but i'm not sure about that). But often you want to write to the sink from different tasks (e.g. this example takes messages sent from one websocket connection, and broadcasts it onto every other connected websocket, so the sink for each websocket needs to be accessed by every other websocket handler task), and you can't do that with only the sink as you can't clone it. Either need to wrap it into a Mutex and clone that around the different tasks (and lock it every time you need to write to it, like OP did originally) or you can use forward to map the rx (receiver) of a channel to the sink, and clone the tx (sender) part of the channel for each task that wants to write to the sink. That way, you only have one task that is accessing the sink directly, so no issues with synchronization.

Has anyone worked with websockets before? Particularly with the tokio-tungstenite crate? I'm getting a Protocol(ResetWithoutClosingHandshake) error in my request. I send in some text, and i'm supposed to receive an audio file back.

tokio-tungstenite

i based my code mostly on the client example from the tokio-tungstenite project: https://github.com/snapview/tokio-tungstenite/blob/master/examples/client.rs

For a much simpler but less flexible approach there's wasm-pack for creating JS packages from Rust, and wasm-bindgen for easy interop. Both have very good documentation.

After four years, I found some time to pay that deb-tech (yes, quite a long time, eh). To make it fun I rewrote everything from scratch in SolidJS, which went smooth thanks to this amazing library p5js-wrapper. For WASM, C++ is still a good choice, but what about Rust? I did some research and found wasm-pack. A few lines in the cargo.toml file and we were ready to generate compiled + ready to import bytecode!

Support using wasm-pack in Worklets (particularly AudioWorklet) #689

If you're looking to use it to interface with node/browsers, then try wasm-pack.

Webassembly: wasm-bindgen 0.2.83 / wasm-pack 0.10.3

wasm-pack has bugs - it publishes a module which declares itself as a commonjs module. (You can fix that by manually adding "type": "module" in package.json). Then the web build should work with other bundlers. I opened an issue about this over a year ago. There's a PR and everything, but no movement :/

wasm-pack helps you build Rust-generated WebAssembly packages and use it in the browser or with Node.js.

Is the Rust WASM ecosystem being half dead better? wasm-pack and wasm-bindgen are barely maintained anymore, and trust me it's not because everything works flawlessly…

I've been learning Rust for the past few weeks and have been enjoying it a lot.

- The community is very helpful on Discord (https://discord.com/invite/rust-lang-community).

- The package ecosystem (crates.io) makes it very easy to find and import things, and they're consistently documented.

- There's a path to compiling on web via WebAssembly (https://rustwasm.github.io/wasm-pack/)

In a few weeks of learning the language, I managed to put together this visualization: https://twitter.com/admiralakk/status/1542560489091350529

But realistically, either Go or Rust will be fine. You should pick the one you're more likely to stick with and learn, even when it gets tough. I've found the community aspect to be very helpful, because then at least I know I'm not the only idiot out there.

There are various ways to set up a web project that uses Svelte, Wasm, and Rust. For example, wasm-pack from the rust-wasm group provides a template for simple HTML-CSS-JS applications. There are also several project templates for React or Svelte with Rust and Wasm.