Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Computadores - HP Integrity NonStop H-Series (16.73 mb)
Computadores - HP Integrity NonStop H-Series (957.56 kb)
Computadores - HP Integrity NonStop H-Series (881.66 kb)
Computadores - HP Integrity NonStop H-Series (965.62 kb)
Computadores - HP Integrity NonStop H-Series (676.93 kb)
Computadores - HP Integrity NonStop H-Series (393.72 kb)
Computadores - HP Integrity NonStop H-Series (776.57 kb)
Facilidade de uso
OSF DCE Application Development Guide—Core Components
convert between code set names and identifiers.
15.3.3.3 Tag-Setting Routine
Recall from Section 15.3.1 that operations that specify international characters as input
and output parameters declare special code set tag parameters. The purpose of these
parameters is to hold the unique identifier for the code set into which the input or output
data is to be encoded when it is transferred over the network.
The function of the tag-setting routine is to provide a way to set an operation’s code set
tag parameters to specific code set values from within the stubs rather than in the
application code. The application specifies the name of the tag-setting routine as the
argument to the cs_tag_rtn ACF attribute; the client and server stubs call this routine
when the operation is invoked to set the tag parameters to specific network code set
values before they call the stub support routines for buffer-sizing and code set
conversion. The stubs use the network code set values returned by the tag-setting routine
as input to the buffer-sizing and conversion routines. In turn, these routines compare the
network code set values to be used for input and output data to the local code set in use
for the data, and determine whether or not new buffer allocation and code set conversion
are necessary.
When called from the client stub, the tag-setting routine sets the sending tag parameter to
the code set to use for input character data. If the client expects output character data
from the server, the routine also sets the desired receiving tag parameter to the code set
that the client prefers the server to use for sending back the output data. On the client
side, the buffer-sizing routines local_type_name_net_size( ) and the code set conversion
routines local_type_name_to_netcs() use the value in the sending tag as the network
code set value to use for transmitting the input data. When the input data arrives at the
server
side,
the
server
stub
uses
the
sending
tag
as
input
to
the
local_type_name_local_size( )
buffer-sizing
routine
and
the
local_type_name_from_netcs( ) code set conversion routines, which use the value to
determine whether or not new buffer allocation and conversion is necessary from the
network code set to the local code set.
When called from the server stub, the tag-setting routine sets the receiving tag parameter
to the code set to use for transmitting the output character data back to the server. The
routine can use the desired receiving tag value as input to determine the most appropriate
code set in which to encode output data for the client. On the server side, the buffer-
sizing routines local_type_name_net_size( ) and the code set conversion routines
local_type_name_to_netcs() use the value in the receiving tag as the network code set
value to use for transmitting the output data. When the output data arrives at the client
side, the client stub uses the receiving tag as input to the local_type_name_local_size( )
buffer-sizing routine and the local_type_name_from_netcs() code set conversion
routines, which use the value to determine whether or not new buffer allocation and
conversion is necessary from the network code set to the local code set.
DCE RPC provides one tag-setting routine named rpc_cs_get_tags() that applications
can use to set code set tag values within the stubs. To use this routine, specify its name
as the argument to the cs_tag_rtn attribute and link your application with the DCE
library. The example ACF for the cs_test interface specifies the rpc_cs_get_tags()
15−14
Tandem Computers Incorporated
124245
... Este manual também é adequado para os modelos :
Computadores - HP Integrity NonStop J-Series (1.2 mb)
Computadores - HP NonStop G-Series (1.2 mb)
Computadores - HP NonStop L-Series (1.2 mb)