reqwest

reqwest copied to clipboard

We love reqwest, but we also need to use websocket. :-)

Warp implements it at server-side, so it would be nice if reqwest could implement it at client-side allowing we to reuse all other features (e.g: TLS support) present in reqwest.

Cheers

Curious, why would you use websockets outside a browser context?

Some cryptocurrency exchange provide websocket API! ex. https://docs.pro.coinbase.com/#websocket-feed https://www.bitstamp.net/websocket/v2/ https://docs.kraken.com/websockets/

I'm using ws-rs, but it's not support async/await. It would be great if reqwest can support websocket!

Curious, why would you use websockets outside a browser context?

At the company, we are going to use websocket specially for sales terminal(s) monitoring, but there are many other features which websockets are useful outside a web browser, like real time gaming, embedded system remote control, industrial machine full-duplex communication via dedicated boards like STM32 and so on.

Another use-case, the Kubernetes API server exposes a bunch of streaming stuff (e.g exec, port-forward) over websockets.

Is there any plan for support WebSockets ?

Curious, why would you use websockets outside a browser context?

I need websockets for integration testing.

It would be nice if reqwest supported websockets to allow reverse proxying of servers using websockets with something like https://crates.io/crates/warp-reverse-proxy like go reverse proxy does.

Given that reqwest is building support for WebAssembly for use in web context, supporting websockets in wasm could be a great ergonomics improvement over using web-sys manually.

Curious, why would you use websockets outside a browser context?

An other data point: Chrome's DevTools protocol uses bidirectional websockets as its baseline transport.

It also supports custom pipes but that's not really easy to do in rust, and obviously only works when the controller is also the creator of the chrome instance.

Curious, why would you use websockets outside a browser context?

I'm building a client side application which needs to maintain an established connection with a web server so the web server can periodically send some instructions back to the client machine. Doing this with websockes would greatly improve the experience.

Curious, why would you use websockets outside a browser context?

Like the above, I'm building an embedded client application, controlled remotely via events from another app. One can send commands there that are fetched by the client machines, but instead of polling every 5 or so seconds to see if there's any new event, I'd like to use websockets for faster delivery and near real-time processing.