could not find `async_std` in `async_tungstenite` about async-tungstenite HOT 11 CLOSED

Yes.
https://docs.rs/async-tungstenite/0.3.1/async_tungstenite/

from async-tungstenite.

Including a link to those on README.md would be a good idea.

from async-tungstenite.

There's a link to the docs in the README.md and the second section mentions the part about the feature flags. Can you suggest a way how to make this more obvious, maybe with a PR to change it accordingly?

from async-tungstenite.

Exactly the same problem.
The link above doesn't explain anything.
Please tell me if there is anything else I need to do to use it besides:

[dependencies]
async-tungstenite = "*"

?

from async-tungstenite.

You need to enable the async-std-runtime cargo feature for getting async-std support. See the list at https://github.com/sdroege/async-tungstenite#what-is-async-tungstenite for more details.

Do you have suggestions how to make this more obvious?

from async-tungstenite.

Above (or below) this list, write the same example as in the example with dependencies, which will indicate the section and what needs to be added to it. For example:

[features]
default = ["async-std-runtime"]
async-std-runtime = ["async-std", "async-tungstenite/async-std-runtime"]

Peeped here.
But it doesn't work.

from async-tungstenite.

Can you give a full example that doesn't work for you?

from async-tungstenite.

This worked:

[features]
default = ["async-std-runtime"]
async-std-runtime = ["async-tungstenite/async-std-runtime"]

But, the echo example fails on connection:
Err(Http(Response { status: 200, version: HTTP/1.1, headers: {"x-amz-id-2": "w6IM8TOcdq894Xx+f1Ecis9/tVZ3k2hLY765z9W0oFvA4TYKLv9dylOP2D0itDGyaHI6kpwGzh4=", "x-amz-request-id": "VYWZNTCSS9A77Q1C", "date": "Wed, 07 Sep 2022 11:44:27 GMT", "last-modified": "Thu, 26 Aug 2021 03:35:42 GMT", "etag": "\"6d5a28f4c5e297e95a29988884c9e896\"", "content-type": "text/html", "server": "AmazonS3", "content-length": "4413", "connection": "close"}, body: None }))

from async-tungstenite.

The server apparently replies with HTML instead of the websocket protocol upgrade. Can you create an issue for that?

from async-tungstenite.

Apparently, this is due to the fact that it no longer works.
echo.websocket.org
This service is no longer available.

from async-tungstenite.

Indeed. If you know an alternative we can switch to that here :)

from async-tungstenite.