try adding websocket support with no tungstenite dependence

[Lori-Shu]

I am tring to implement websocket in reqwest. Although there is lib like reqwest_websocket that has good support, most rely on tungstenite, I am wondering if I can remove the dependence ,please review.

[Lori-Shu]

@linyihai did my commits make sense or I just head to wrong direction? Still have no idea how to exact trailer map from response and pass to client, Do you think it is needed to be implemented? Please take a look when you are around. Thanks.

[seanmonstar]

Thanks for giving this a try!

I don't believe this is quite the direction that they were asking about. At least, what I understood from the issue is the desire to be able to access the trailers on any given response.

So, the addition of something like this:

impl Response {
    pub async fn trailers(&mut self) -> crate::Result<Option<HeaderMap>> {
        // get this from the `http_body::Body` trailers frame
    }
}

[Lori-Shu]

impl Response {
    pub async fn trailers(&mut self) -> crate::Result<Option<HeaderMap>> {
        // get this from the `http_body::Body` trailers frame
    }
}

I just write my version of fn trailers, Thanks for the instruction..

[Lori-Shu]

I have no idea if the Upgraded type is safe io parallel, Just want to make WebSocket type safe for parallel io.

[Lori-Shu]

I've tried #2812, maybe give you a possible solution or way, if I ran out of context again, sorry for your time. @seanmonstar