A single protocol strategy was adopted, namely GIOP, as the native protocol for communications between OmniORB clients and servers. This avoids performance hits from multiplexing and reduces the number of layers. Unnecessary multiplexing is eliminated. Multithreaded runtime is designed to maximise concurrency and minimise unnecessary thread overhead. No thread switching is involved along the call chain as shown by a diagram.
Alternative approaches involve serialisation bottlenecks in multiprocessor machines.
A diagram showing dynamic call connection management was shown. The approach adopted avoids dynamic deadlock problems. Connections are closed after an idle period. Diagrams showing transport buffer management, and marshalling optimisations were shown. Large buffer allocation for marshalling is avoided in OmniORB, requiring 2 passes when GIOP 1 is used.