Method and system for providing version control of parameters in a command-based API using Java serialization

• US 7,409,693 B2
• Filed: 10/30/2003
• Issued: 08/05/2008
• Est. Priority Date: 10/30/2003
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: McCain, Brian S., Therrien, Amy L.
• Primary Examiner(s): Nguyen; Van H.
• Application Number:
  US10/697,761
• Publication Number:
  US 20050097575A1
• Time in Patent Office: 1,741 Days
• Field of Search: 719310-313, 719315-316, 719/328, 719/330, 709201-203, 709217-219
• US Class Current: 719/328
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

A technique for determining whether a server host supports the functions in a command sent by a client host. The client host formulates a command including a command object that contains parameter objects. The parameter objects, which represent the functions, are serialized, e.g., using the Java serialization command, and communicated to the server host. The server host attempts to deserialize the parameter objects. If it is successful, it is concluded that the server host supports the functions represented by the parameter objects. Or, it is concluded that the server host is incompatible with the functions represented by one or more parameter objects that cannot be deserialized. The server host may be a storage server, and the functions may be storage-related, such as a copy type to be performed.

Claims

1. A method for providing a command from a client-side host to a server-side host, comprising:

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;

serializing the command and parameter objects to provide serialized command and parameter objects; and

sending the serialized command and parameter objects to the server-side host as the command to determine whether said server-side host supports said different function,

receiving the serialized command and parameter objects at the server-side host as the command from the client-side host;

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 method 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 method of claim 1, wherein:

the client-side API comprises a client-side of a command-based API.

4. The method of claim 3, wherein:

the server-side host uses a server-side API of the command based API to attempt to deserialize the serialized command object and all parameter objects.

5. The method of claim 1, further including:

receiving the error message from the server-side host that said function is not supported;

locating a second server-side host that supports said function; and

communicating the serialized command and the parameter objects to the second server-side host.