Currently there is no ability for an LTP Engine to receive blocks (i.e. handle sessions) from peer engines that are not pre-configured. I attempted a local patch to add a default receive configuration (LtpEngineConfig object) to the LtpUdpEngineManager but because the reception callbacks are on the LtpUdpEngine there was no way for the received block to be indicated to the engine's user (BPA).
If the LtpUdpEngineManager were to relay callbacks from its contained engines then the engine user could bind callbacks on the manager and not care about which particular engine was the receiver of the session.
Currently there is no ability for an LTP Engine to receive blocks (i.e. handle sessions) from peer engines that are not pre-configured. I attempted a local patch to add a default receive configuration (
LtpEngineConfigobject) to theLtpUdpEngineManagerbut because the reception callbacks are on theLtpUdpEnginethere was no way for the received block to be indicated to the engine's user (BPA).If the
LtpUdpEngineManagerwere to relay callbacks from its contained engines then the engine user could bind callbacks on the manager and not care about which particular engine was the receiver of the session.