Technical data

Chapter 5 117
Technical Articles
DCE to RPC 1.2.1
[min_is(a,,c)] long g5[*..7][2..9][*..8]; /* g5[-10..7][2..9][-30..8] */
[min_is(a,b,)] long g6[*..10][*..20][3..8]; /* g6[-10..10][-20..20][3..8] */
[max_is(,,e),min_is(a)] long g7[*..1][2..9][3..*]; /*
g7[-10..1][2..9][3..25] */
[min_is(a,,c),max_is(,d,e)] long g8[*..1][2..*][*..*];/*
g8[-10..1][2..15][-30..25] */
Support for IDL encoding Services:
This extension to the IDL stub compiler will enable instances of one or more data types to
be encoded into and decoded from a byte stream format suitable for persistent storage
without invoking RPC Runtime.
The encode and decode attributes are used in conjunction with IDL Encoding service
routines (idl_es*) to enable RPC applications to encode datatypes in input parameters into
a byte stream and decode datatypes in output parameters from a byte stream without
invoking the RPC runtime. Encoding and decoding operations are analogous to marshaling
and unmarshalling, except that the data is stored locally and is not transmitted over the
network.
Support for User defined Exceptions
This extension to the IDL compiler will allow specification of a set of user-defined
exceptions that may be generated by the server implementation of the interface. If an
exception occurs during the execution of the server, it terminates the operation and the
exception is propagated from server to client.
Support for Customized Binding handles
This enhancement allows the application developer to add some information that the
application wants to pass between the client and server. This can be used when
application-specific data is appropriate to use for finding a server when the data is also
needed as a procedure parameter.
References
For details on the features of IDL refer to the below mentioned RFC :
• Reference: RFC2.1: Proposed Enhancements for DCE 1.1 IDL, J. Harrow, July, 1992.
URL: http://www.opengroup.organization/tech/rfc/
• OSF DCE Application Development Guide -- Core Components Vol. - II (Revision 1.1)