Paulo Lopes

Initial step in commit: 05100c0f8ea4842e19992d5d52da55c4750db95d

I think we could implement this purely as a helper class as it could open the door to other things, for example, a redis backed cluster manager, as it would...

Hi @norbald, I think this is a usability issue. We should document that when using vert.x in cluster mode (cluster client) users, should manage their connection. The expectation is that...

I've been trying to reproduce this issue in master, I've been increasing the values until it crashes, but on my side it seems to happen at REDIS side: ```java @Test...

@barbarosalp can you, verify that the issue still happens on `master`? we're getting close to a 4.0.0 release, so backporting fixes is getting hard as the codebases are quite appart...

Hi @cdennison the goal with the commit you mention was to respect what redis states about commands, for `SCAN` we can see: ``` 127.0.0.1:6379> command info scan 1) 1) "scan"...

@alexellis @jconlon This pr got lost on my side. Yes, we should upgrade it to 4.0.0. One of the improvements, application wize there should be almost to none code changes...

Yes, this will always parse the request body. For security or latency reasons not everyone might want/need it, but is a quick solution. In the refered issue about upgrading the...

Yes you can get the raw body, by replicating what the `BodyHandler` is doing, on the request object, add a handler that will receive the chunks of the HTTP body...

@alexellis please have a look at the PR and the discussion about upgrading the template. I believe this PR would make it easier to support all features of vert.x and...