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.

Abstract: A server side scripting language hosts batch requests from a client for invoking object specific libraries on the client requestor. The requestor executes a user application driven by a web scripting language which may not have facilities or resources for efficiently invoking operations that are provided by the server. A batch script enables the requestor to invoke a set of server operations in batch, without exchanging requests and result for each invocation of a service side operation, thus mitigating the bandwidth that would otherwise occur for individual client/server exchanges for each operation. The server provides a proxy class for expected object types and operations, and a dispatch layer identifies the appropriate proxy class for each operation requested from the batch script.