## Building An Application for Character and Code Set Interoperability

An application programmer who wishes to design his or her RPC application for character and code set interoperability performs the following steps:

1. Writes the interface definition file (.idl) to include constructs that will enable automatic code set conversion during remote procedure execution.

2. Writes an associated attribute configuration file (.acf ) for the interface that includes ACF attributes that will enable automatic code set conversion during remote procedure execution.

3. Writes the stub support routines that client and server stubs use to carry out automatic code set conversion during a remote procedure call. You can omit this step if you use the stub support routines supplied with DCE.

4. Writes the server code and includes the steps to get the server's supported code sets and export them to the name service database, and to remove them from the name service database upon termination or exit.

5. Writes the client code and includes the steps to set up the character and code set evaluation mechanism.

6. Writes the character and code set compatibility evaluation routine. You can omit this step if you use one of the evaluation routines supplied with DCE.

Note that building an RPC application for character and code set interoperability imposes some restrictions on the application. For example, an application that uses the RPC character and code set interoperability features cannot use customized binding handles. See The cs_char Attribute for more details on internationalized RPC application restrictions.

The next topics describe the steps just outlined in more detail.

More:

Writing the Interface Definition File

Writing the Attribute Configuration File

Writing the Stub Support Routines

Writing the Server Code

Writing the Client Code

Writing the Evaluation Routine

###