- CORBA does not mandate that there be one kind of OA but only one was specified
- The BOA was under specified and vendors had to extend it to make it useful
- As a result, source code was not very portable
- CORBA 2.3 resolved this issue with the Portable Object Adapter (POA) and deprecated the older BOA
- Older C++ orbs may provide the BOA for compatibility.
- The POA is well specified and uses a flexible policy-based approach to configuration
- POA-based implementations should be source-code portable
|