Ben Ashford

Hello, Thanks for raising this, it's an interesting problem. By the sounds of the description your diagnosis in the third paragraph is probably correct. A `future::join_all` will run each future...

Ah OK, I can see it now. This is an interesting edge-case. When the call to `send` is made on the connection, the outgoing message is serialised and added to...

Hello, Thanks for this 👍 This is quite a big PR so I'll some more comments later once I have the chance to go in to some of the details...

At present there's no specific support for this. But individual applications can send an `AUTH` command explicitly when opening a connection. This can be cumbersome depending on the nature of...

You can do that with the paired connection: https://docs.rs/redis-async/0.6.2/redis_async/client/paired/fn.paired_connect.html So a rough example would be: ```rust let connection = client::paired_connect(&addr) .await .expect("Cannot open connection"); let result = connection.send(resp_array!["EVAL", "return 1",...

Thanks for this, it's very interesting. I'll take a look into `reqwest`, there may well be some lessons we can learn from it. I also think there's a few other...

`rs-es` started as just supporting the query API and has been gradually growing outwards to include everything else in the ElasticSearch API. As @RoxasShadow there is a preliminary module already,...

There's not really any written rules, rather the goal to be consistent with: a) itself, b) Rust conventions, and c) ElasticSearch conventions. In reality there's a lot of conflict here,...

Thanks @polyfractal, that makes sense. It seems unlikely a project like this would need to support them.

Would make sense if #42 were implemented first.