Daniel Abramov

Yes, it could have been more convenient, but `reqwest` is by its nature a batteries included wrapper around HTTP, whereas `tungstenite-rs` is more like a core for support of WebSockets...

> Improve parsing Sec-WebSocket-Extensions. I did in https://github.com/hyperium/headers/pull/88, but we can include that here for now if necessary. NB: Should we probably wait a bit for a merge of the...

@kazk thanks for the investigation! The corresponding PRs have been merged.

Unfortunately it's not being worked on, but the PRs are welcome ;)

> an alternative might be to change text/binary to take an Into directly Another approach would be to implement https://github.com/snapview/tungstenite-rs/issues/96 similar to the way it was tried to be implemented...

> I have some mostly finished code that removes the need to make the data a unique copy when applying the mask that I was originally going to put into...

> When will this be fully merged? I think it's a very nice feature and doesn't make stuff too complex. It has some unresolved merge conflicts. It seems like replacing...

> I don't see how Bytes can help without unsafe. > I have data allocated with libc::malloc and want to send them via web socket. What I mean is that...

@Dushistov, so for your particular question the workaround would be to create `Vec` from the data that you allocated with `libc` and then pass it to the library. The only...

> if tungstenite only want to own data then this is not problem, wraper around allocated data has proper Drop implementation that call libc::free, so it is actually like Vec...