Abstract: A method and system for synchronizing a main database of a server and a local database of a handheld device. A user can use an application residing in the handheld device to make transactions in the local database. During a synchronization operation, the handheld device and server are coupled. The system then determines whether the application should be updated and, if so, causes the server to provide an update. The system also causes the handheld device to provide to the server information related to the transactions made by the user to the local database. The system causes the server to perform transactions on the main database based on the transaction information. The system also causes the server to extract data from the main database. The server can then provide at least some of the extracted data to the handheld device to update the local database.

Abstract: A method and system for synchronizing a main database of a server and a local database of a handheld device. A user can use an application residing in the handheld device to make transactions in the local database. During a synchronization operation, the handheld device and server are coupled. The system then determines whether the application should be updated and, if so, causes the server to provide an update. The system also causes the handheld device to provide to the server information related to the transactions made by the user to the local database. The system causes the server to perform transactions on the main database based on the transaction information. The system also causes the server to extract data from the main database. The server can then provide at least some of the extracted data to the handheld device to update the local database.

Abstract: A method and system for synchronizing a main database of a server and a local database of a handheld device. A user can use an application residing in the handheld device to make transactions in the local database. In a synchronization operation, a synchronization client is used to: establish a connection between a server and the synchronization client; receive an identifier for the main database's structure from the server; receive an identifier for the version of the handheld application from the server; send transaction information to the server; receive metadata to update the handheld application; and receive data extracted from the main database from the server. The synchronization client is also used to update filter information used by the server to reduce the size of the data downloaded to the handheld device.

Abstract: The A method and system for server synchronization with a computing device via a companion device is disclosed. In one embodiment, the method comprises synchronizing a device and an enterprise server via a companion device, which comprises retrieving a record extraction sequence from the server; providing the record extraction sequence to the handheld device from the companion device; and extracting records stored on a database according to the record extraction sequence, wherein the extracted records are not already stored on the computing device.

Abstract: A handheld device performs a data update process to synchronize locally stored data with data from another device, which may be stored in different formats. The handheld device gets the size of the data from the other device. The handheld device applies a scaling factor to the size. The handheld device compares the scaled size to the amount of free memory in the handheld device available for the data update process. The handheld device receives the update data if there is sufficient memory available. Otherwise, the handheld device does not receive the update data in order to conserve power in the handheld device. The handheld device can also perform an error routine to notify the user of the insufficient memory condition and to allow the user to make more memory available.

Abstract: A method and system for direct server synchronization with a computing device is disclosed. In one embodiment, the method comprises synchronizing directly a handheld device and an enterprise server, which comprises retrieving a record extraction sequence from the server; and extracting records stored on a database according to the record extraction sequence, wherein the extracted records are not already stored on the computing device.

Abstract: A method and system for synchronizing a main database of a server and a local database of a handheld device. A user can use an application residing in the handheld device to make transactions in the local database. During a synchronization operation, the handheld device and server are coupled. The system then determines whether the application should be updated and, if so, causes the server to provide an update. The system also causes the handheld device to provide to the server information related to the transactions made by the user to the local database. The system causes the server to perform transactions on the main database based on the transaction information. The system also causes the server to extract data from the main database. The server can then provide at least some of the extracted data to the handheld device to update the local database.

Abstract: The A method and system for server synchronization with a computing device via a companion device is disclosed. In one embodiment, the method comprises synchronizing a device and an enterprise server via a companion device, which comprises retrieving a record extraction sequence from the server; providing the record extraction sequence to the handheld device from the companion device; and extracting records stored on a database according to the record extraction sequence, wherein the extracted records are not already stored on the computing device.

Abstract: A handheld device performs a data update process to synchronize locally stored data with data from another device, which may be stored in different formats. The handheld device gets the size of the data from the other device. The handheld device applies a scaling factor to the size. The handheld device compares the scaled size to the amount of free memory in the handheld device available for the data update process. The handheld device receives the update data if there is sufficient memory available. Otherwise, the handheld device does not receive the update data in order to conserve power in the handheld device. The handheld device can also perform an error routine to notify the user of the insufficient memory condition and to allow the user to make more memory available.

Abstract: A method and apparatus for transferring information in synchronizing a server and a handheld device. The information is binary information that is then compressed using a suitable compression algorithm. The compressed binary data is then text encoded using a suitable text encoding algorithm. The text encoded information is then encoded according to a protocol associated with the connection between the server and the handheld device. For example, the server can perform the compression and encoding operations on database data to be downloaded to the handheld device to reduce the time needed to transfer the information between the server and the handheld device.

Abstract: A method and system for synchronizing a main database of a server and a local database of a handheld device. A user can use an application residing in the handheld device to make transactions in the local database. In a synchronization operation, a synchronization client is used to: establish a connection between a server and the synchronization client; receive an identifier for the main database's structure from the server; receive an identifier for the version of the handheld application from the server; send transaction information to the server; receive metadata to update the handheld application; and receive data extracted from the main database from the server. The synchronization client is also used to update filter information used by the server to reduce the size of the data downloaded to the handheld device.

Abstract: The A method and system for server synchronization with a computing device via a companion device is disclosed. In one embodiment, the method comprises synchronizing a device and an enterprise server via a companion device, which comprises retrieving a record extraction sequence from the server; providing the record extraction sequence to the handheld device from the companion device; and extracting records stored on a database according to the record extraction sequence, wherein the extracted records are not already stored on the computing device.

Abstract: A method and system for synchronizing a main database of a server and a local database of a handheld device. A user can use an application residing in the handheld device to make transactions in the local database. During a synchronization operation, the handheld device and server are coupled. The system then determines whether the application should be updated and, if so, causes the server to provide an update. The system also causes the handheld device to provide to the server information related to the transactions made by the user to the local database. The system causes the server to perform transactions on the main database based on the transaction information. The system also causes the server to extract data from the main database. The server can then provide at least some of the extracted data to the handheld device to update the local database.

Abstract: Methods and apparatus for hosting a network service on a cluster of servers, each including a primary and a secondary Internet Protocol (IP) address. A common cluster address is assigned as the secondary address to each of the servers in the cluster. The cluster address may be assigned in UNIX-based servers using an ifconfig alias option, and may be a ghost IP address that is not used as a primary address by any server in the cluster. Client requests directed to the cluster address are dispatched such that only one of the servers of the cluster responds to a given client request. The dispatching may use a routing-based technique, in which all client requests directed to the cluster address are routed to a dispatcher connected to the local network of the server cluster. The dispatcher then applies a hash function to the client IP address in order to select one of the servers to process the request.

Abstract: A method and system for direct server synchronization with a computing device is disclosed. In one embodiment, the method comprises synchronizing directly a handheld device and an enterprise server, which comprises retrieving a record extraction sequence from the server; and extracting records stored on a database according to the record extraction sequence, wherein the extracted records are not already stored on the computing device.

Abstract: A language recognition methodology is provided whereby any finite-state model of context may be used in a very general class of decoding cascades, and without requiring specialized decoders or full network expansion. The methodology includes two fundamental improvements: (1) a simple generalization, weighted finite-state transducers, of existing network models, and (2) a novel on-demand execution technique for network combination. With the methodology of the invention one or more of the network cascades are formulated as a finite state transducer, and is composed, for a selected portion of the network, with a next successively higher level of the network cascade to prescribe a mapped portion of that next successively higher level corresponding to the portion of the network cascade selected to be expanded.

Abstract: An application module (A) running on a host computer in a computer network is failure-protected with one or more backup copies that are operative on other host computers in the network. In order to effect fault protection, the application module registers itself with a ReplicaManager daemon process (112) by sending a registration message, which message, in addition to identifying the registering application module and the host computer on which it is running, includes the particular replication strategy (cold backup, warm backup, or hot backup) and the degree of replication associated with that application module. The backup copies are then maintained in a fail-over state according to the registered replication strategy. A WatchDog daemon (113), running on the same host computer as the registered application periodically monitors the registered application to detect failures.

Abstract: An application module (A) running on a host computer in a computer network is failure-protected with one or more backup copies that are operative on other host computers in the network. In order to effect fault protection, the application module registers itself with a ReplicaManager daemon process (112) by sending a registration message, which message, in addition to identifying the registering application module and the host computer on which it is running, includes the particular replication strategy (cold backup, warm backup, or hot backup) and the degree of replication associated with that application module. The backup copies are then maintained in a fail-over state according to the registered replication strategy. A WatchDog daemon (113), running on the same host computer as the registered application periodically monitors the registered application to detect failures.

Abstract: By checkpointing and restoring a user application process, that includes a volatile state and a persistent state, recovery of an application process from the checkpoint position is possible. Specifically, a volatile state is checkpointed in a checkpoint position. Next, the persistent state is monitored to detect a file operation following a checkpoint position that will modify the persistent state. Then, portions of the persistent state are checkpointed if a modification of the persistent state is about to be performed. Then, a recovery to the checkpoint position can be performed such that modifications to the persistent state since the checkpoint position are undone. This allows for resumption of the user application process from the checkpoint position.

Abstract: A checkpoint and restoration system is disclosed to provide checkpoint and restoration techniques for user application processes which save the process state, including the volatile state and desired portions of the persistent state, during normal execution, and thereafter restore the saved state. A lazy checkpoint technique is disclosed which delays the taking of the persistent state checkpoint until an inconsistency between the checkpointed volatile state and a portion of the persistent state is about to occur. The disclosed checkpoint and restoration system allows a user or a user application process to specify selected portions of the persistent state to be excluded from a checkpoint. A selected portion of the pre-restoring process state, such as a return value argument, may be protected before restoring the user application process to a checkpointed state, so that the pre-restoration values of the protected state are retained following restoration of the checkpoint.