[SERVER-24479] Make the 'Notification' class be able to return a value Created: 08/Jun/16 Updated: 14/Jul/16 Resolved: 12/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 16 (06/24/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
We have places in the server, which need to use a std::promise-like kind of synchronization, which can pass back a result. We should extend the Notification class so it can support returning a value. |
| Comments |
| Comment by Githook User [ 15/Jun/16 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: Notification isn't default-movable because it contains a mutex and a condition_variable. |
| Comment by Githook User [ 12/Jun/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Ian Whalen (Inactive) [ 12/Jun/16 ] |
| Comment by Githook User [ 10/Jun/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Kaloian Manassiev [ 08/Jun/16 ] |
|
The wait methods will accept operation context and will support cancelability. |
| Comment by Andrew Morrow (Inactive) [ 08/Jun/16 ] |
|
How would that differ from future<void> or shared_future<void>? |