## Checklist

If you plan to use MateComponent Activation for your own CORBA servers, you should use the following simple checklist.

- Create a unique UUID for your CORBA server by using libuuid and uuidgen (both are available by anonymous ftp from tsx-11.mit.edu in `/pub/linux/packages/ext2fs`. These are part of the `e2fsprogs` package.

- Create a proper `.server` file for your server describing its IDL interfaces, its main properties and the way it is to be activated.

- Call `matecomponent_activation_init` (make sure you do not initialize twice by calling `matecomponent_activation_is_initialized`). Then, call `matecomponent_activation_active_server_register` to register yourself as running to the MateComponent Activation daemon.

If you are a client willing to activate a few servers, it is a little simpler: you just must make sure you call the `matecomponent_activation_init` function and you can then call `matecomponent_activation_query` or `matecomponent_activation_activate` or `matecomponent_activation_activate_from_id`.

Here, put a real-life example of a client and a server.

### The non-local case

Here, present how to use setup the system for the non-local case. If anyone is willing to write this part, mail mate-components-list@gnome.org. in the meantime, you can have a look at the code in mate-libs HEAD from cvs. (I never had time to go look at it)