What is T3 and why was it developed? When is it mandated and when is it optional?
T3 provides a framework for messages in WebLogic Server that provide support for performance enhancements, such as abbreviations and features like object replacement (which work in the context of WebLogic Server clusters and HTTP and other product tunneling). T3 predates Java Object Serialization and RMI, while closely tracking and leveraging these specifications. T3 is a superset of Java Object Serialization or RMI; anything you can do in Java Object Serialization and RMI can be done over T3. T3 is mandated between WebLogic Servers and between programmatic clients and a WebLogic Server cluster. HTTP and IIOP are optional protocols that can be used to communicate between other processes and WebLogic Server. It depends on what you want to do. For example, when you want to communicate between a browser and a WebLogic Server, use HTTP; between an orb and a WebLogic Server, use IIOP.
