Conduit manager for occasionally-connected application server
First Claim
1. An occasionally-connected application server comprising:
- a synchronization unit configured to synchronize data nodes with a client for an application, the application including an occasionally-connected data model; and
a conduit manager configured to translate between data from external systems and the data nodes defined by the occasionally-connected data model.
1 Assignment
0 Petitions
Accused Products
Abstract
Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a metadata description of the mobile application'"'"'s anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.
-
Citations
24 Claims
-
1. An occasionally-connected application server comprising:
-
a synchronization unit configured to synchronize data nodes with a client for an application, the application including an occasionally-connected data model; and
a conduit manager configured to translate between data from external systems and the data nodes defined by the occasionally-connected data model. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method comprising:
-
at a server, synchronizing data nodes with a client for an application including an occasionally-connected data model; and
at the server, translating between data from external systems and the data nodes defined by the occasionally-connected data model. - View Dependent Claims (9, 10, 11, 12)
-
-
13. An occasionally-connected application server comprising:
-
memory to store an occasionally-connected data model; and
a cache to store data nodes as defined by the occasionally-connected data model, wherein the occasionally-connected application server caches data nodes in the cache as indicated by metadata in the occasionally-connected data model. - View Dependent Claims (14, 15, 16, 17, 18, 19)
-
-
20. The occasionally-connected application server of claim 20, wherein synchronization of the data nodes between the occasionally-connected application server and the client can be done in the background.
-
21. An occasionally-connected application server comprising:
-
a first component configured to synchronize data nodes with a client for an application, the application including an occasionally-connected data model; and
a second component configured to translate between data from external systems and the data nodes defined by the occasionally-connected data model.
-
-
22. A system including:
an occasionally-connected application server configured to provide an application to a client, the application allowing a client to read and update application data without requiring current access to the occasionally-connected application server, the occasionally-connected application server adapted to obtain application data from an external system to send to the client, wherein the occasionally-connected application server is adapted to translate data from the external system into data nodes. - View Dependent Claims (23, 24)
Specification