The only place in the 2.0 drivers where you can specify custom codecs is while building the DseSession:
The customer I'm working with wants to be able to specify these type codecs dynamically when initiating his driver application. To do this, they need to start the session and look at the structures to have all the information they need to specify the codecs. Then, they have to spin up a new DseSession object.
Can we add something like:
This functionality was available in the 1.x driver paradigm.