## Problem Statement There is a growing list of properties being added to both `RedisConnection` and `RedisConnectionPool` that can be simplified with `Configuration` types. This will also enable RediStack to provide features such as URL parsing, rather than requiring users to interact with **SwiftNIO**'s `SocketAddress` directly. ## Proposed Solution A starting point might be accepting Vapor's [`RedisConfiguration`](https://github.com/vapor/redis/blob/master/Sources/Redis/RedisConfiguration.swift). ## Alternatives N/A - I know I want this.