-
Notifications
You must be signed in to change notification settings - Fork 992
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
Reactive support #68
Comments
4.x package: New interfaces:
|
Open issues: Collection resultsWhat about collection result types like lists and sets? Should these be dissolved into particular elements? IterablesSync API: // sync API
List<String> result = redis.hkeys("..."); Rx API: // either
Observable<String> result = redis.hkeys("...");
// or
Observable<List<String>> result = redis.hkeys("..."); MapsSync API: // sync API
Map<String, String> result = redis.hmget("..."); Rx API: // either
Observable<KeyValue<String, String>> result = redis.hmget("...");
// or
Observable<Map<String, String>> result = redis.hmget("..."); PubSubProvide hot observables for subscription listeners? ClusterProvide observable commands also for node-selection commands? (Commands executed on multiple cluster nodes) |
What would be the advantage of emitting Grouping could be done using |
None. Rx does not differentiate between one and many elements. Dissolving If you approach from pure Rx dissolved elements are welcome, but if you're used to |
Btw. nice to hear from you @xasx |
* Use completeable commands instead of async commands in rx API * Provide PubSub observers and reactive PubSub API * Extend tests * Extend test timeouts
Observables emit single elements and |
Add another layer between command creation and execution (today a command is created and immediately executed). Reactive commands should be only executed (example from RxJava as soon as
call
is invoked).This layer could be located between the command builder and the async connection itself.
The text was updated successfully, but these errors were encountered: