Abstract: A method of synchronizing data elements between devices can include receiving at a first device, from only one of multiple peer devices with which the first device is configured to synchronize, a request to synchronize data between the first device and the only one peer device; identifying data elements stored in the first device that have changed since a previous synchronization operation between the first device and the only one peer device; and transmitting, directly and solely to the only one peer device, for each of the identified data elements, a local data identifier and a corresponding change to be applied to a data element in the only one peer device that corresponds to the local data identifier. In some implementations, each local data identifier is transmitted in a format in which it is maintained in the first device.

Abstract: To enable the peer-to-peer synchronization among multiple devices, each device in the peer network keeps track of the changes it makes to any shared data and also keeps track of its own knowledge of the changes made by other devices. When two or more peer devices communicate, they share with each other their information about any changes made to the shared data by them or by other devices. This allows the devices to synchronize with each other to the extent that each of the devices knows what changes have been made by it or by other devices in the peer network.

Abstract: To enable the peer-to-peer synchronization among multiple devices, each device in the peer network keeps track of the changes it makes to any shared data and also keeps track of its own knowledge of the changes made by other devices. When two or more peer devices communicate, they share with each other their information about any changes made to the shared data by them or by other devices. This allows the devices to synchronize with each other to the extent that each of the devices knows what changes have been made by it or by other devices in the peer network.

Abstract: A method of synchronizing data elements between devices can include receiving at a first device, from only one of multiple peer devices with which the first device is configured to synchronize, a request to synchronize data between the first device and the only one peer device; identifying data elements stored in the first device that have changed since a previous synchronization operation between the first device and the only one peer device; and transmitting, directly and solely to the only one peer device, for each of the identified data elements, a local data identifier and a corresponding change to be applied to a data element in the only one peer device that corresponds to the local data identifier. In some implementations, each local data identifier is transmitted in a format in which it is maintained in the first device.

Abstract: A system enables data synchronization for data files shared between or among multiple devices. When a shared data file is modified on one of the computing devices, metadata describing or otherwise enabling recreation of that modification are generated. To enable synchronization of the shared data file, the metadata—rather than the modified shared data file—are transmitted to other devices. These other systems can then use the metadata to recreate the modification of the shared data file and thus achieve data synchronization without requiring retransmission of the shared data file after each modification thereto.

Abstract: Data communication networks allow data, such as electronic documents, graphical images or audio files, to be retrieved from remote sources for use in local applications, such as synchronization environments. A device may store metadata useable to navigate and locate data stored on the remote source, and an application on the device may use the stored metadata to determine what data to retrieve from the remote server based on the currently accessed data. The metadata may comprise a portion of the data on the remote source that is displayed on the device while the data are being retrieved.

Abstract: A game table comprises first and second substantially parallel player sides extending along a length direction, first and second substantially parallel goal sides extending along a width direction and a game playing surface defined within the player and goal sides. The game table includes at least one pivoting handle assembly connected to the game table via a pivot connection. The handle assembly includes at least one turning rod carrying at least one player member, and a handle engaged with the turning rod whereby turning the handle operates to rotate the player to strike a playing piece. The handle assembly is configured to pivot about the pivot connection above the game playing surface in a pivot plane substantially parallel to the game playing surface.

Abstract: In a medical information system, a facility is provided so that different application programs can share information about their current state, so that a user of these applications can move more efficiently among them. This facility includes a patient context interface (PCI) that each application can access by means of an application programming interface (API). This API provides mechanisms by which applications can register their identity and their interest in certain types of data and events. The PCI stores data received from applications for sharing with other applications, and the PCI notifies certain applications of events received from other applications. In operation, an application that is used to review data for a patient stores (in the PCI) an identification of the patient whose data is currently being reviewed, and another application retrieves (from the PCI) that patient identification so that it can automatically present that patient's data when the user switches to that application.