Methods and systems for coupling client-side and server-side persistence frameworks

• US 8,655,910 B1
• Filed: 10/28/2009
• Issued: 02/18/2014
• Est. Priority Date: 10/28/2009
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Naresh, Rakshith, Kumar, Rupesh
• Primary Examiner(s): Lee, Wilson
• Assistant Examiner(s): Hershley, Mark E
• Application Number:
  US12/607,391
• Time in Patent Office: 1,574 Days
• Field of Search: 707/802, 707/803, 707/809, 707/812, 707/770
• US Class Current: 707/770
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 7/00 Methods or arrangements for processing data by operating upon the order or content of the data handled logic circuits H03K19/00
• CPC Class Codes: G06F 9/4493 Object persistence

Abstract

A client application can be configured to use a client-side persistence framework to maintain a local database for use in storing data even when a data provider is not available. In accordance with the present subject matter, the client application can be configured to obtain and rely on server-side persistence metadata rather than requiring the persistence metadata to be specifically included in the code for the client-side application. In some instances, this can simplify the development process and/or allow for more robust client-side applications.

Claims

1. A method, comprising

detecting, by a client application executed using a processor, a request for object data to a remote data provider;

determining, by the client application, that persistence metadata related to the object data is locally available, wherein the persistence metadata describes how the object data is stored using one or more database structures;

determining, by the client application, version information of the persistence metadata;

transmitting, by the client application processor, the request for the object data to a remote data provider, wherein the request comprises the version information of the persistence metadata related to the object data;

receiving, by the client application, the object data from the remote data provider in response to the request for the object data;

receiving updated persistence metadata associated with the object from the data source in response to the request for the object data identifying that the version information is outdated; and

storing the object data in a local database using the updated persistence metadata, wherein using the updated persistence metadata comprises storing the object data in an updated storage scheme described by updated persistence metadata that is different than an outdated storage scheme described by the persistence metadata.

2. The method set forth in claim 1,

wherein maintaining the object data in memory comprises storing an object in volatile memory, and

wherein storing the object data in the local database comprises storing data in nonvolatile memory.

3. The method of claim 2, wherein the locally-available persistence metadata is accessible via a bus to a tangible computer-readable medium and wherein transmitting the request for the object data to the remote data provider comprises transmitting the request via a network connection to the remote data provider.

4. The method set forth in claim 1, further comprising:

updating the local database structure based on whether the updated persistence metadata is received.

5. The method set forth in claim 1, wherein the persistence metadata comprises at least one of:

data mapping object parameters to database columns, wherein the updated persistence data changes the data mapping of object parameters to database columns,

data identifying a relationship between the object and another object, wherein the updated persistence data changes the relationship between the object and the other object,

data identifying join columns for the database, wherein the updated persistence data changes the join columns for the database,

a loading parameter for use in loading data from the database, wherein the updated persistence data changes the loading parameter, or

a cascading option, wherein the updated persistence data changes the cascading option.

6. The method set forth in claim 1,

wherein storing the object data in the local database comprises storing a plurality of parameter values of the object in corresponding columns of a table in the database.

7. The method set forth in claim 6,

wherein the object is an instance of a class, and

wherein each row of the table corresponds to an object that is an instance of the class.

8. The method set forth in claim 6,

wherein the object is an instance of the class and the object data comprises a plurality of records, and

wherein each row of the table corresponds to one of the plurality of records.

9. The method of claim 1, wherein the locally-available persistence metadata is stored at the same computing system at which the processor executes.

10. A computing system comprising a processor with access to a tangible computer readable medium embodying program components, the program components comprising:

an application that configures the computing system to request data representing an object from a data provider and store the data representing the object in memory, the object comprising an instance of an class, wherein the class defines a property and the object is represented in memory by a value for the property;

a persistence framework that configures the computing system to utilize persistence metadata to maintain a local database, the local database including an entry corresponding to the object, and the persistence metadata is related to the data representing the object, wherein the persistence metadata describes how the object data is stored using one or more database structures;

a metadata exchange module that configures the computing system to;

obtain updated persistence metadata from the data provider, wherein the metadata exchange module further configures the computing system to detect the request for data representing the object and obtain the updated persistence metadata from the data provider based on a locally available persistence metadata is outdated; and

update the local database if the persistence metadata available from the data provider represents an updated version of the persistence metadata, wherein updating the local database comprise storing the object in an updated storage scheme described by updated persistence metadata that is different than an outdated storage scheme described by the persistence metadata that is outdated.

11. The system set forth in claim 10, wherein the local database is maintained in a nonvolatile computer-readable medium.

12. The system set forth in claim 10, wherein the object is represented in memory as a set of parameter values and the entry for the object in the local database comprises a value in a column of a database table, each column of the database table corresponding to a respective property and each row of the database table corresponding to an instance of the class.

13. The system set forth in claim 10, wherein the metadata exchange module configures the computing system to obtain the persistence metadata when obtaining data representing the object.

14. A computer program product comprising a non-transitory computer-readable medium embodying program code executable by a computing system, the program code comprising:

program code for detecting a request for object data;

program code for determining that persistence metadata related to the object data is locally available, wherein the persistence metadata describes how the object data is stored using one or more database structures;

program code for determining version information of persistence metadata related to the object data;

program code for transmitting the request for the object data to a remote data provider, wherein the request comprises the version information;

program code for receiving object data from the remote data provider in response to the request for the object data;

program code for receiving updated persistence metadata associated with the object from the data source in response to the request for the object data identifying that the version information is outdated; and

program code for storing the object data in a local database using the updated persistence metadata, wherein using the updated persistence metadata comprises storing the object data in an updated storage scheme described by updated persistence metadata that is different than an outdated storage scheme described by the persistence metadata.

15. The computer program product set forth in claim 14,

wherein the program code for maintaining the object data in memory comprises code for storing an object in volatile memory, and

wherein the program code for storing the object data in the local database comprises program code for storing data in nonvolatile memory.

16. The computer program product set forth in claim 14, further comprising:

program code for updating the local database structure based on whether the updated persistence metadata is received.

17. The computer program product set forth in claim 14, wherein the persistence metadata comprises at least one of:

data mapping object parameters to database columns,

data identifying a relationship between the object and another object,

data identifying join columns for the database,

a loading parameter for use in loading data from the database, or

a cascading option.

18. The computer program product set forth in claim 14,

wherein storing the object data in the local database comprises storing a plurality of parameter values of the object in corresponding columns of a table in the database.