Parameter driven data format conversion in client/server architectures

• US 9,201,938 B2
• Filed: 05/21/2012
• Issued: 12/01/2015
• Est. Priority Date: 05/21/2012
• Status: Active Grant

• Current Assignee: GradeCam, LLC
• Original Assignee: SAP SE
• Inventors: Fischer, Martin, Schmidt, Olaf
• Primary Examiner(s): Etienne, Ario
• Assistant Examiner(s): SHIU, HO T
• Application Number:
  US13/476,996
• Publication Number:
  US 20130311546A1
• Time in Patent Office: 1,289 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/116 Details of conversion of file system types or formats
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

A system and method for parameter driven data format conversion in a client/server architecture are disclosed. A format conversion framework is provided in a protocol layer between the client and the server. The format conversion framework passes a format conversion identifier (ID) with a request from the client from the client to the server. A conversion module is looked up by the format conversion framework based on the format conversion ID, the conversion module providing a conversion routine. The format conversion framework then executes the conversion routine on a result returned from the server to the client based on the request, the conversion routine converting a format of the result into a format used by the client.

Claims

1. A method for parameter driven data format conversion in a client-server architecture comprising a server and a plurality of clients, the method comprising:

providing a format conversion framework in a protocol layer between a client of the plurality of clients and the server;

passing, by the format conversion framework from the client to the server, a format conversion identifier (ID) of a plurality of format conversion identifiers with a request from the client, each format conversion identifier being specific to a corresponding client of the plurality of clients;

looking up a conversion module of a plurality of conversion modules by the format conversion framework based on the format conversion ID such that the looked-up conversion module is specific to the format conversion ID, the conversion module providing a corresponding conversion routine; and

executing, by the format conversion framework, the corresponding conversion routine on a result returned from the server to the client based on the request, the corresponding conversion routine converting a format of the result into a format used by the client, the format used by the client being one of a rich site summary (RSS) format, an extensible markup language (XML) format, a javascript object notation (JSON) format, and an open data protocol (ODATA) format, the format used by the client being different from a format used by other one or more clients of the plurality of clients.

2. The method in accordance with claim 1, further comprising sending, to the client, the result in the format used by the client.

3. The method in accordance with claim 1, wherein looking up the conversion module includes accessing a format conversion registry.

4. The method in accordance with claim 1, wherein the conversion module is selected from the format conversion registry based on the format conversion ID.

5. The method in accordance with claim 4, wherein executing the corresponding conversion routine further comprises calling the corresponding conversion routine from the looked-up conversion module.

6. The method in accordance with claim 1, wherein passing the format conversion ID with the request further comprises passing the request through a protocol handler.

7. A system for parameter driven data format conversion in a client-server architecture comprising a server and a plurality of clients, the system comprising:

a protocol handler at the server that handles a result from the server based on a request from a client of the plurality of clients, the result being provided according to a server protocol;

a format conversion framework provided between the client and the server, the format conversion framework comprising;

a format conversion registry that stores a plurality of conversion identifiers (IDs) that specifies a conversion routine needed for the request from the client, each conversion identifier associated with a corresponding conversion routine, at least one conversion identifier (ID) being passed from the client to the server;

a format converter interface that calculates a format conversion registered according to one of the plurality of conversion identifiers; and

a format converter handler communicating with the protocol handler to look up a conversion module from a plurality of conversion modules that specify executable conversion routines, the format converter handler executing the conversion routine from the conversion module on the result from the server needed for the request from the client, the converted result being in a format usable by the client, the format usable by the client comprising one of a rich site summary (RSS) format, a javascript object notation (JSON) format, and an open data protocol (ODATA) format, the format usable by the client being different from a format usable by other one or more clients of the plurality of clients.

8. The system in accordance with claim 7, wherein the format converter handler further sends, to the client, the result in the format used by the client.

9. The system in accordance with claim 7, wherein the conversion module is selected from the format conversion registry based on the format conversion ID.

10. A non-transitory computer-readable medium containing instructions to configure a processor to perform operations comprising:

providing a format conversion framework in a protocol layer between a client of a plurality of clients and a server connected in a client-server architecture;

passing, by the format conversion framework from the client to the server, a format conversion identifier (ID) of a plurality of format conversion identifiers with a request from the client, each format conversion identifier being specific to a corresponding client of the plurality of clients;

looking up a conversion module by the format conversion framework based on the format conversion ID, the conversion module providing a conversion routine; and

executing, by the format conversion framework, the conversion routine on a result returned from the server to the client based on the request, the conversion routine converting a format of the result into a format used by the client, the format used by the client being one of a rich site summary (RSS) format, a javascript object notation (JSON) format, and an open data protocol (ODATA) format, the format used by the client being different from a format used by other one or more clients of the plurality of clients.

11. The computer-readable medium in accordance with claim 10, further comprising sending, to the client, the result in the format used by the client.

12. The computer-readable medium in accordance with claim 10, wherein looking up the conversion module includes accessing a format conversion registry.

13. The computer-readable medium in accordance with claim 10, wherein the conversion module is selected from the format conversion registry based on the format conversion ID.

14. The computer-readable medium in accordance with claim 13, wherein executing the conversion routine further comprises calling the conversion routine from the conversion module.

15. The computer-readable medium in accordance with claim 10, wherein passing the format conversion ID with the request further comprises passing the request.