Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor internally to use sendCommandAsRESP throughout #10

Open
kjessup opened this issue Mar 23, 2018 · 0 comments
Open

Refactor internally to use sendCommandAsRESP throughout #10

kjessup opened this issue Mar 23, 2018 · 0 comments

Comments

@kjessup
Copy link
Member

kjessup commented Mar 23, 2018

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."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant