Good day. Could you clarify the reasoning behind the removal of OpProcessors support in TP 4.0 and what extension mechanics are proposed as an alternative?
Example of how we use OpProcessors for protocol extensions: 1. Extension of core OpProcessors - during TX processing, IDs of our elements undergo two phases: temporary and permanent. During which their values are changed. Because query results are streamed, we send additional metadata that maps temporary IDs to the permanent ones to keep client data in sync in the final response Frame. 2. We provide our own OpProcessor, which handles commands related to the management of database instances present on the server. Which mechanics are provided for such and similar extension points in TP 4?
