With these changes applied, the Factory now defaults to automatically selecting the correct transport protocol in its executor-stack. It will always try to send it over the more efficient UDP transport first. If this query yields a size related issue (truncated messages), it will retry over a streaming TCP/IP transport.
It's still possible to explicitly specify the udp:// or tcp:// URI scheme in order force using only the UDP or TCP-based executor stacks respectively. This explicit choice continues to exist mostly for rare special cases and debugging purposes.