Oliver Wangler

@koush what is your take on this?

I wonder what you would think of adding a custom implementation to Android to figure out the system resolver config. According to [this Stackoverflow post](https://stackoverflow.com/questions/3070144/how-do-you-get-the-current-dns-servers-for-android) the universal solution to this...

Any news on this? I suppose, managing tun devices via `NetworkManager` makes sense and there are more potentially more users benefiting from it.

> Maybe look into the shiplift crate so you don't create a docker api client from scratch. Thanks for the hint, will give it a spin then!

You can do it by jumping through some hoops using `hyper`: ```rust use futures::{Future, TryFutureExt}; use hyper::{server::Server, service::make_service_fn}; use std::convert::Infallible; use std::net::SocketAddr; use warp::filters::BoxedFilter; use warp::Reply; /// Create a hyper...

You're right, you can't. The original issue description is misleading then though, maybe you could clarify the missing behaviour a bit more.

> Just seeing this now, but [datachannel-rs](https://github.com/lerouxrgd/datachannel-rs) is also a solution. The advantage is that it focuses on WebRTC Data Channels so it's lightweight (no media capture, encoding/decoding, etc) Which...

Based on @allada's example, the following is a bit more concise and good enough for testing: ```rust fn setup_stream Request { let body = Body::wrap_stream(s.map(|m| Ok::(m.encode_to_vec().into()))); let mut codec =...

I'd like to warm this up, as this is vastly superior to the `grpc-web` approach (mostly about hitting the connection limit per host imposed by browsers for multiple streaming requests)....

Any progress on that front?