[SERVER-39113] Add handleInternalRequest to ServiceEntryPoint API Created: 22/Jan/19  Updated: 06/Dec/22  Resolved: 18/Apr/19

Status: Closed
Project: Core Server
Component/s: Internal Client
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Sprint: Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25
Participants:

 Description   

This is meant as an alternative to using DBDirectClient, which sets the 'inDirectClient' flag on the passed-in OperationContext, and so cannot be used to run operations under a session.

handleInternalRequest will behave similarly to DBDirectClient, except will take (or create) a "fresh" OperationContext and not set the 'inDirectClient' flag on it (though it will grant internal authorization to it).

This method is essentially syntactic sugar: it should take a BSONObj request, serialize it into an OpMsgRequest, call handleRequest on the OpMsgRequest, and deserialize the response into a BSONObj.



 Comments   
Comment by Esha Maharishi (Inactive) [ 18/Apr/19 ]

Closing as Won't Fix. The attached cr has become outdated as of SERVER-40223, which effectively instead made AsyncWorkScheduler::scheduleRemoteCommand the "syntactic sugar" for sending a command to the local node through the service entry point.

Generated at Thu Feb 08 04:51:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.