-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Service Arch
So far we have been focusing on changing out the IDL infrastructure, which includes calls that are handled by automatically generated code. However, classes built using the IDL generator can also be manually called in hand-rolled code, and where we manually create these objects we may need to either create and populate serialization context objects to pass in, or we will need to pass these serialization context objects in from some outer parent object.
The majority of the work here will be to seek out where we manually create these objects, and to determine the context in which they are being used. This will give us the direction needed to figure out what modifications are needed. During the course of work for SERVER-74284, we have marked off a number of TODOs that show possibly affected sites, as well we should scrutinize calls to the parseNamespaceFromRequest() and parseNamespaceFromDoc() and see if we need to pass in SerializationContext objects at these sites.
- depends on
-
SERVER-73108 Handle command request/reply serialization/deserialization
- Closed
-
SERVER-74284 Fix existing tests for command serialization/deserialization
- Closed
-
SERVER-77723 Turn parseNamespaceFromRequest calls to deserialize in IDL
- Closed
-
SERVER-78486 Replace parseNamespaceFrom* calls with deserialize
- Closed
- is depended on by
-
SERVER-70547 Create multitenancySupport passthroughs that inject a tenant prefix and security token
- Closed
- related to
-
SERVER-85552 Complete TODO listed in SERVER-75930
- Closed