[JAVA-1554] Get rid of MongoFuture Created: 14/Nov/14 Updated: 04/Nov/16 Resolved: 27/Nov/14 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Async |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Ross Lawley |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Async |
| Description |
|
In core, just use SingleResultCallback. In driver-async, overload methods, one that takes a SingleResultCallback, the other which does not and returns a regular Future. |
| Comments |
| Comment by Githook User [ 30/Jan/15 ] |
|
Author: {u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}Message: Removed MongoFuture in favour of just using callbacks
|
| Comment by Ross Lawley [ 15/Dec/14 ] |
|
Hi dwursteisen we've removed RxJava support in favour of reactive stream support - see This provides more flexibility for users as there are already multiple reactive stream implementations, including RxJava. Cheers, Ross |
| Comment by Wursteisen David [ 15/Dec/14 ] |
|
This commit just remove the rx version of the async driver. Will you introduce it (again) later ? Is it still part of your roadmap ? |
| Comment by Ross Lawley [ 27/Nov/14 ] |
|
Hi nscavell just to let you know this has landed - its a big change (hopefully the last before we stabilise the api). It fixes some of the issues that MongoFuture had and also should be a cleaner way to use the async driver for end users. I'm hoping that you find it cleaner for interacting with the async driver but feel free to reach out with any feedback. Cheers, Ross |
| Comment by Githook User [ 27/Nov/14 ] |
|
Author: {u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}Message: Removed MongoFuture in favour of just using callbacks
|