OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
dce_db_header_t header; /* Header must be first! */
/* (server-specific data goes here) */
} XXX_data_t;
void XXX_data_convert(
[in] handle_t h,
[in, out] XXX_data_t *data
[out] error_status_t *st
);
}
It should be compiled with the following Attribute Configuration File (ACF), which
instructs the idl compiler to write the data conversion routine into the XXX_cstub.c file:
interface XXX
{
[encode, decode] XXX_data_convert([comm_status] st);
}
5.5 The IDL Encoding Services
When remote procedure call sends data between a client and a server, it serializes the
user’s data structures by using the IDL encoding services, described in Chapter 16 of this
book.
5.5.1 Encoding and Decoding in the Backing Store
The backing store uses this same serialization scheme for encoding and decoding,
informally called pickling, when storing data structures to disk. The IDL compiler, idl,
writes the routine that encodes and decodes the data. This routine is passed to
dce_db_open( ), remembered in the handle, and used by the following store and fetch
routines:
• dce_db_fetch( )
• dce_db_fetch_by_name()
• dce_db_fetch_by_uuid( )
• dce_db_header_fetch( )
• dce_db_store()
• dce_db_store_by_name( )
• dce_db_store_by_uuid( )
5− 4 Tandem Computers Incorporated 124245