1. A program storage device, tangibly embodying a program of instructions executable by a server-side host to perform a method for processing a command from a client-side host, the method comprising:
receiving a serialized command and parameter objects at the server-side host as the command from the client-side host, the serialized command and parameter objects obtained by invoking a client-side application programming interface (API) at the client-side host to pass in a set of parameter objects, and to provide a command object that contains the parameter objects, wherein each of the parameter objects represents a different parameter of a command, said different parameter representing a different function and each new parameter for the command is defined as a unique new class type, and serializing the command and parameter objects to provide serialized command and parameter objects;
deserializing, by said server-side host, the serialized command and parameter objects to determine whether the server-side host is compatible with the different parameters of the command that are represented by the parameter objects, the server-side host determining that the server-side host is not compatible with one or more of the different parameters if the server-side host does not support a class type associated with said one or more of the different parameters, and
reformulating, by said client-side host, the command to delete one or more parameters determined to be incompatible, wherein:
if the server-side host cannot successfully deserialize at least one of the serialized parameter objects, the server-side host sends an error message to the client-side host to inform the client-side host that the server-side host does not support the parameter represented by the at least one serialized parameter object that cannot be successfully deserialized.
2. The program storage device of claim 1, wherein:
the server-side host cannot successfully deserialize the serialized parameter objects whose class type is not recognized by the server-side host.
3. The program storage device of claim 1, wherein:
the server-side host uses a server-side API of a command based API to attempt to deserialize the serialized command and all parameter objects.
4. The program storage device of claim 3, wherein:
the serialized command and parameter objects are obtained at the client-side host by invoking a client-side API at the client-side host that comprises a client-side of the command-based API.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A bonding method of a ceramic honeycomb structure formed by bundling a plurality of porous honeycomb segments through adhesive layers, where the porous honeycomb segments are provided with numerous circulation holes partitioned by partition walls and penetrated in an axial direction,
wherein the respective pieces of the porous honeycomb segments are stacked while interposing the adhesive layers between respective adhered surfaces, and
the porous honeycomb segments are bonded together by performing main pressurization on the whole through the porous honeycomb segments located on an outermost layer after stacking a predetermined number of pieces.
2. The bonding method of a ceramic honeycomb structure according to claim 1,
wherein the respective porous honeycomb segments are subjected to preliminary pressurization at the time of stacking by weaker pressure than the main pressurization.
3. The bonding method of a ceramic honeycomb structure according to claim 2,
wherein the preliminary pressurization is performed at pressure equal to or below 0.5 kgfcm2.