public interface ClientRequestInfo extends ClientRequestInfoOperations, RequestInfo, IDLEntity
对一些属性和操作ClientRequestInfo是不是在所有的拦截点有效。 下表显示每个属性或操作的有效性。
如果它无效，尝试访问它将导致BAD_INV_ORDER被抛出与14的标准次要代码。
request_id
yes yes yes yes yesoperation
yes yes yes yes yesarguments
yes1 no yes no noexceptions
yes no yes yes yescontexts
yes no yes yes yesoperation_context
yes no yes yes yesresult
no no yes no noresponse_expected
yes yes yes yes yessync_scope
yes no yes yes yesreply_status
no no yes yes yesforward_reference
no no no no yes2get_slot
yes yes yes yes yesget_request_service_context
yes no yes yes yesget_reply_service_context
no no yes yes yes ClientRequestInfo-specific:target
yes yes yes yes yeseffective_target
yes yes yes yes yeseffective_profile
yes yes yes yes yesreceived_exception
no no no yes noreceived_exception_id
no no no yes noget_effective_component
yes no yes yes yesget_effective_components
yes no yes yes yesget_request_policy
yes no yes yes yesadd_request_service_context
yes no no no noClientRequestInfo传递给send_request时，每个参数的列表中都有一个条目，无论是在inout还是out中。
但是只有in和inout参数才可用。reply_status贡献不是LOCATION_FORWARD ，访问此属性将抛出BAD_INV_ORDER标准的次要代码为14。
ClientRequestInterceptor
add_request_service_context,
effective_profile,
effective_target,
get_effective_component,
get_effective_components,
get_request_policy,
received_exception_id,
received_exception,
target
arguments,
contexts,
exceptions,
forward_reference,
get_reply_service_context,
get_request_service_context,
get_slot,
operation_context,
operation,
reply_status,
request_id,
response_expected,
result,
sync_scope
_create_request,
_create_request,
_duplicate, _get_domain_managers,
_get_interface_def,
_get_policy, _hash, _is_a,
_is_equivalent,
_non_existent,
_release, _request,
_set_policy_override