•LOCATION_FORWARD replies to asynchronous messages (i.e., OP_ONEWAY) will fail as the current system does not generate reply futures, and thus the original request is not stashed anywhere to be re-dispatched on receipt of the FORWARD reply.

•LOCATION_FORWARD and sstUpdateLocation (LOCATE_REQUEST/REPLY) messages may result in destructive modification of the original remote reference and loss of the IOR. It is not clear from CORBA 2.1 Standard, Section 12.6 - Object Location whether it should be the client-side SST responsibility to maintain the original IOR and space information through successive forwardings after connection closures. If it is, this is not done currently. You should hold onto original IOR strings or the SstIor object so they can revert to an original.

•Implicit binding for IDL union types is not supported by SST. The explicit binding (with classes conforming to the CORBAUnion protocol) must be used.

•Marshaling of IDL any values is currently limited for some of the base types. At present, only the most generic type information is supported. For example, an object that might be represented as an IDL short is always marshaled as an IDL long.