The library currently sends commands in the 'inline' format rather than using the REdis Serialization Protocol (see docs ). The 'inline' approach has a much smaller limit than RESP in terms of the size of the data that can be sent in for example a SET command.

By adding public func sendCommandAsRESP these limits can be avoided when necessary.

Perhaps in time the library can be refactored internally to use sendCommandAsRESP throughout, but I don't currently have time to do this.

ISS-551 Fixed. Description: When LRANGE a large bulk, for example, 80 char per line, then if fetching over 100 lines then LRANGE will raise a BAD_ACCESS exception. 
Reason: recursive bytes extraction causes thread unsafe buffer access.

Fixed by threading with recv(fd) without recursive exactBytesFromBuffer().

Issue encountered:

When transmitting json strings to redis (via LPUSH/LPUSHX) after using jsonEncodedString(), the values were being rejected. The situation was remedied by encoding the string with a leading and trailing single quote character instead of double quotes. To accomplish this, I needed extensions[1]. However, toString() in RedisValue and the sendCommand used within listPrepend and listPrependX were subject to "internal protection level" compilation errors.

Proposed solution: Add "public" to sendCommand() and toString() so downstream users can make tweaks in edge cases such as mine.

[1] Example extensions (mild tweaks on top of existing implementations):

extension RedisClient.RedisValue { func toStringForRedis() -> String { switch self { case .string(let s): return "'(s)'" default: return self.toString() } } }

extension RedisClient { func listPrepend(key: String, jsonRedisValues: [RedisValue], callback: @escaping redisResponseCallback) { self.sendCommand(name: "LPUSH (key) (jsonRedisValues.map { $0.toStringForRedis() }.joined(separator: " "))", callback: callback) } }

• I've used XCTFail instead of XCTEqual(false..., due to this now the the two test classes are not consistent. I'm not sure what's the preferred way of failing the tests, but as soon as I get a comment I can change it to be consistent one way or the other.
• Please review it carefully, this is my first swift code.
• If the size of the PR is too big I can break it up into several smaller ones

Version ranges "Version(0,0,0)..<Version(10,0,0)" were generating exceptions when building:

Package.swift:28:85: error: no '..<' candidates produce the expected contextual result type 'Version'

Package.swift:28:85: note: overloads for '..<' exist with these result types: Range, CountableRange

from @sportlabsMike

"Perhaps in time the library can be refactored internally to use sendCommandAsRESP throughout"

"The library currently sends commands in the 'inline' format rather than using the REdis Serialization Protocol (see docs ). The 'inline' approach has a much smaller limit than RESP in terms of the size of the data that can be sent in for example a SET command.

By adding public func sendCommandAsRESP these limits can be avoided when necessary.

Perhaps in time the library can be refactored internally to use sendCommandAsRESP throughout, but I don't currently have time to do this."