Json mapping

Ice types are mapped to following json types:

Basic Types

User-Defined Types

TypeIds Optimization

As in ice protocol data encoding, TypeID could be transferred using a type ID compression scheme to avoid repeatedly marshaling the same type ID strings. In that case the response json will contain an IceT array with 0 based indexed type IDs and for classes the "iceId" field will indicate the index in IceT for the corresponding type.

Slicing

In a future release, TypeID slicing will be supported. For classes having ancestors, all of them will be recorded in reverse order (using TypeIds Optimization) after the most derived type. The iceId json param, in case of any ancestor, will be an array of int instead of a single int.

Examples