Abstract: Certain embodiments facilitate developing an application using a client-side object model to data source mapping. This may involve defining data use on the client side of the application in various ways that simplify the development necessary to implement data access features. In certain embodiments, data access and synchronization between a client and a data source is accomplished by configuring the client to map to a set of remote procedure call operations for a given data source. For example, the user may implement or confirm update, create, delete, and retrieve function calls for a given data source such that the application can implement data access and updating using those functions. Embodiments use persistent object identifiers, change logs, and/or data bindings in a client to provide various features and benefits. Certain embodiments also facilitate conflict resolution, demand paging, and lazy loading.

Abstract: Certain embodiments facilitate developing an application using a client-side object model to data source mapping. This may involve defining data use on the client side of the application in various ways that simplify the development necessary to implement data access features. In certain embodiments, data access and synchronization between a client and a data source is accomplished by configuring the client to map to a set of remote procedure call operations for a given data source. For example, the user may implement or confirm update, create, delete, and retrieve function calls for a given data source such that the application can implement data access and updating using those functions. Embodiments use persistent object identifiers, change logs, and/or data bindings in a client to provide various features and benefits. Certain embodiments also facilitate conflict resolution, demand paging, and lazy loading.