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

Re-implement using streams #2

Open
rpj opened this issue Dec 17, 2018 · 1 comment
Open

Re-implement using streams #2

rpj opened this issue Dec 17, 2018 · 1 comment
Assignees
Labels
enhancement New feature or request nice-to-have Would be nice, but in not required for functionality.

Comments

@rpj
Copy link
Owner

rpj commented Dec 17, 2018

Redis 5.0 landed the feature that this code base half-implements! The examples in the docs are even sensor-based! Re-implement using streams, obviously. (Will need relatively wide adoption of v5, though)

@rpj rpj self-assigned this Dec 17, 2018
@rpj rpj added major-feature More than an "enhancement" nice-to-have Would be nice, but in not required for functionality. labels Dec 18, 2018
@rpj rpj added P3 Priority 3 P4 Priority 4 and removed P3 Priority 3 labels Jan 3, 2019
@rpj
Copy link
Owner Author

rpj commented Jan 7, 2019

Honestly not even a P4, as things work just fine and in fact very similarly to the way they would using Streams, and in a backwards-compatible way to boot. Moving tags, though I'll probably just close this as NTBF eventually.

@rpj rpj added enhancement New feature or request and removed P4 Priority 4 major-feature More than an "enhancement" labels Jan 7, 2019
@rpj rpj changed the title Re-implement using streams! Re-implement using streams Jan 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request nice-to-have Would be nice, but in not required for functionality.
Projects
None yet
Development

No branches or pull requests

1 participant