wire_marshal

typedef [wire_marshal(wire_type)] type-specifier userm-type;

unsigned long __RPC_USER  < userm_type >_UserSize(
    unsigned long __RPC_FAR *pFlags,
    unsigned long                      StartingSize,
    < userm_type >  __RPC_FAR * pUser_typeObject );

unsigned char __RPC_FAR * __RPC_USER  < userm_type >_UserMarshal(
    unsigned long  __RPC_FAR * pFlags,
    unsigned char __RPC_FAR * Buffer,
    < userm_type >  __RPC_FAR * pUser_typeObject);

unsigned char __RPC_FAR * __RPC_USER  < userm_type >_UserUnmarshal(
    unsigned long  __RPC_FAR *  pFlags,
    unsigned char __RPC_FAR *  Buffer,
    < userm_type >  __RPC_FAR * pUser_typeObject);

void __RPC_USER  < userm_type >_UserFree(
    unsigned long  __RPC_FAR * pFlags,
    < userm_type >  __RPC_FAR * pUser_typeObject);

userm-type

Specifies the id of the user data type to be marshaled. It can be any type, as given by the type-specifier,.as long as it has a well-defined size. The userm-type need not be remotable but must be a type known to the MIDL compiler.

wire-type

Specifies the named transfer data type that is actually transferred between client and server. The wire-type must be a MIDL base type, predefined type, or a type identifier of a remotable type.

pFlags

Specifies a pointer to a flag field (unsigned long). The high-order word specifies NDR data representation flags as defined by DCE for floating point, big- or little-endian, and character representation. The low-order word specifies a marshaling context flag. The exact layout of the flags is described in The type_UserSize Function1XXBM65.

StartingSize

Specifies the current buffer size (offset) before sizing the object.

Buffer

Specifies the current buffer pointer.

pUser_typeObject

Specifies a pointer to an object of userm_type.

Example

typedef unsigned long _FOUR_BYTE_DATA;

    typedef struct _TWO_X_TWO_BYTE_DATA { 

        unsigned short low;

        unsigned short high;

        } TWO_X_TWO_BYTE_DATA;

    typedef [wire_marshal(TWO_X_TWO_BYTE_DATA)] _FOUR_BYTE_DATA FOUR_BYTE_DATA;

//Marshaling functions:

unsigned long __RPC_USER FOUR_BYTE_DATA_UserSize(

    ULONG __RPC_FAR * pulFlags,

    char __RPC_FAR * pBufferStart,

    FOUR_BYTE_DATA __RPC_FAR * pul

    );//calculate size that converted data will

      // require in the buffer

unsigned long __RPC_USER FOUR_BYTE_DATA_UserMarshal(

    ULONG __RPC_FAR *pulFlags,

    char __RPC_FAR * pBufferStart,

    FOUR_BYTE_DATA __RPC_FAR * pul

    );//copy FOUR_BYTE_DATA into buffer as

      //TWO_X_TWO_BYTE_DATA

unsigned long __RPC_USER FOUR_BYTE_DATA_UserUnmarshal(

    ULONG __RPC_FAR * pulFlags,

    char __RPC_FAR * pBufferStart,

    FOUR_BYTE_DATA __RPC_FAR * pul

    );//recreate FOUR_BYTE_DATA from TWO_X_TWO_BYTE_DATA

      //in buffer

void __RPC_USER FOUR_BYTE_DATA_UserFree(

    ULONG __RPC_FAR * pulFlags,

    FOUR_BYTE_DATA __RPC_FAR * pul

    );//nothing to do here as the engine frees the top

      //node and FOUR_BYTE_DATA is a flat data type.

Remarks

The wire_marshal attribute specifies a data type that will be used for transmission (the wire-type) instead of an application-specific data type (the userm-type). Each userm-type has a one-to-one correspondence with a wire-type that defines the wire representation of the type. You must supply routines to size the data for marshaling, to marshal and unmarshal the data, and to free memory. Note that if there are embedded types in your data that are also defined with wire_marshal or user_marshal, you need to manage the servicing of those embedded types also. For more information on these routines, see The wire_marshal AttributeXI0SBF.

The wire-type cannot be an interface pointer or a full pointer. The wire-type must have a well-defined memory size. See Marshaling Rules for user_marshal and wire_marshalCP.PJT for details on how to marshal a given wire-type.

The userm-type should not be an interface pointer because these can be marshaled directly. If the user type is a full pointer, you must manage the aliasing yourself.

You cannot use the wire_marshal attribute with the allocate attribute, either directly or indirectly, because the NDR engine does not control memory allocation for the transmitted type.

See Also

The wire_marshal AttributeXI0SBF, user_marshal1K6IH_K, transmit_as9A6WIB, base_types3OJFZI6