Abstract: A system and method for facilitating communications between a mobile device and a network application are provided. A mobile device transmits a request for data change information that includes a time out interval. The network application receives the request and measures a time elapsed since the receipt of the data change request. The network application transmits notification to the mobile device client that the time out interval has elapsed or a network specified time out occurs. As notifications are received or a network time out is detected, the mobile client device tunes the time out interval for subsequent data change requests.

Abstract: Disclosed herein is a set of coordinated game service primitives that allows for custom, per-game, logic. A new game with new custom logic can be added without needing to change any public api or database schema or write any new server code. The same hardware may be shared across many games. And the system scales linearly. That is, if the number of servers is doubled, then so is the number of concurrent users that can be supported. Also disclosed are systems and methods for two-stage aggregation. Pre-aggregation may take place on a plurality of front-end server. Final aggregation may take place on one or more back-end servers. A name value store may be used to reliably store state.

Abstract: Systems and methodologies that facilitate synchronization of a mobile device with a source, via employing a file change tracking database table created in non-volatile memory to designate files for synchronization. The subject invention includes a file modification logger that detects and track changes to files across multiple file systems. The file change tracking database table has a plurality of columns such as: a unique identification column that identifies a file, a file name, previous time the file was changed, and previous time the file was synchronized with a particular machine. A list of files that have changed between a current time and an earlier time can be designated for synchronization, by evaluating when was the file last changed and/or synchronized with a source device (e.g., a desktop, or a lap top.

Abstract: An apparatus and method are directed to maintaining fidelity of a data property during data synchronization. A data property may include virtually any attribute that characterizes an aspect of an application's data. An application may include an email application, contact, calendar, scheduling application, and the like. Data properties may also characterize aspects of a non-application, such as a client's hardware device. Data fidelity is maintained through a concept called herein as property ghosting. Property ghosting leaves selected data properties unchanged on a server when the client device does not send the data property back to the server during data synchronization.