CORBA24 — response_flags in interop draft

n the interop draft (ptc/00-02-04) the response_flags are defined now in terms
of SyncScope. However, SyncScope does only apply to oneway, DII with
INV_NO_RESPONSE, and sendc-stubs with no reply handler. The Messaging
submission explicitly defines that it is ignored in the other cases.

from CORBA Messaging:

interface SyncScopePolicy

This interface is a local object derived from CORBA::Policy. It is applied to
oneway
operations to indicate the synchronization scope with respect to the target of
that
operation request. It is ignored when any non-oneway operation is invoked. This
policy is also applied when the DII is used with a flag of INV_NO_RESPONSE since
the implementation of the DII is not required to consult an interface
definition to
determine if an operation is declared oneway. The default value of this Policy
is not
defined. Applications must explicitly set an ORB-level SyncScopePolicy to ensure
portability across ORB implementations. When instances of SyncScopePolicy are
created, a value of type Messaging::SyncScope is passed to
CORBA::ORB::create_policy. This policy is only applicable as a client-side
override. The client’s SyncScopePolicy is propagated within a request in the
RequestHeader’s response_flags as described in GIOP Request Header.

resolved in interop RTF