[SERVER-1790] replace Future usage with async queries Created: 14/Sep/10  Updated: 12/Jul/16  Resolved: 31/May/11

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 1.9.1

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-928 sort by non-shard key in paralllel Closed
Participants:

 Description   

should have a mode on a connection where you can send a message, then get the response later.



 Comments   
Comment by auto [ 31/May/11 ]

Author:

{u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: Don't use separate threads for Future::spawnCommand SERVER-1790
Branch: master
https://github.com/mongodb/mongo/commit/c4dff971d6ba6bf69b40637168286aaeaaa227f1

Comment by auto [ 31/May/11 ]

Author:

{u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-1790 WIP: use initLazy but still in separate thread
Branch: master
https://github.com/mongodb/mongo/commit/8a2bdb812ce335cdefb6d1688b68ff8e7968502f

Generated at Thu Feb 08 02:58:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.