Custom marshalling allows you to choose your own "on-the-wire" representationof your valuetype. You request custom marshalling by prefixing your valuetypedeclaration in the IDL file with the keyword "custom":custom valuetype MyCustomValue {  // members as usual};Instead of marshalling each member using the default marshalling algorithm,the ORB invokes the methods "marshal" and "unmarshal" on your valuetype thatyou have to implement.`marshal' receives a CORBA::DataOutputStream parameter that offers to writea number of basic types (see mico/include/mico/valuetype.idl). On the re-ceiving end, `demarshal' must extract the same data in the same order.This mechanism could be useful if your valuetype could be transmitted in amore efficient manner than the default of marshalling each data member, orif data must be represented in a certain way using a legacy system.In this example, this is demonstrated by writing and reading a certainsequence of data. For a custom valuetype, `_copy_value()' must invoke thecustom marshalling routines too, and this is what the `test' program checksfor. This example does not make a lot of sense otherwise.