Patent application number | Description | Published |
20080270413 | Client-Specific Transformation of Distributed Data - A data store is distributed between a server and a client. The distributed data store includes global data. A transformation is applied to the global data to generate client-specific data based on the global data. The client-specific data is stored on the client which uses the client-specific data to perform tasks relating to the client-specific data. | 10-30-2008 |
20090006487 | Processing Write Requests with Server Having Global Knowledge - Described are embodiments directed to processing write requests using designated servers with global knowledge of information within a distributed system. The designated servers are used to enforce a data rule that limits the data that may be written to the distributed system. In order to ensure that data written to the distributed system is consistent with the data rule, when another server within the distributed system receives a request to write information that is subject to the data rule, it must consult with one of the designated servers before it can accept the write request. If the designated server determines that the data is consistent with the data rule, the write request is approved. Otherwise, the write request is denied. | 01-01-2009 |
20090006619 | Directory Snapshot Browser - Embodiments of the systems and methods expose a form of backup data, referred to as snapshot data, to an online server. The snapshot data is copy of the directory system at a time in the past. The snapshot data, in embodiments, is exposed as an LDAP server database, which can be manipulated by one or more tools. Thus, the snapshot data is available to online servers to view, to compare, to restore, or to accomplish other actions on the data within the snapshot without server downtime. | 01-01-2009 |
20090006933 | Server Directory Schema Comparator - The embodiments generally relate to systems and methods for determining changes in a directory schema. In embodiments, directory changes are recorded in a change log. The change log may have one or more entries. A determination is made as to which change log entries should be retrieved. Once retrieved, the directory schema changes are determined. In embodiments, the directory changes are then interpreted for presentation to a user. | 01-01-2009 |
20110145208 | POLICY DRIVEN DISTRIBUTED DATA RESILIENCY - A data resiliency layer provides manageable data resiliency policy options for email related applications. Through one or more APIs such applications are enabled to query whether a data resiliency policy is satisfied for a given mailbox or database at a given point in time. Email related applications may consume this information to modify their behavior such as to wait, repeat, or fail the actions at hand to the point where data committal is guaranteed to a degree specified by the data resiliency policy. | 06-16-2011 |
20110145565 | FEDERATED AUTHENTICATION FOR MAILBOX REPLICATION - A data replication mechanism is proposed that relies on existing federation infrastructure enabling distributed authentication instead of storing and using explicit credentials for a remote forest. The data replication mechanism requests a federation token with data replication capabilities targeted to the remote forest and passes this token to the remote forest in lieu of explicit credentials. | 06-16-2011 |
20110167039 | DISTRIBUTED THROTTLING FOR MAILBOX DATA REPLICATION - Distributed mailbox data replication agents are employed to adjust load on mail system resources by enabling the agents to receive a throttling policy, resource capacity, and current usage information. Each agent preparing to access the resource (e.g. provide replicated data) may then throttle itself ensuring optimum resource usage. The agents may receive the information by querying the resource, which monitors accessing agents and their types, or from a shared space instead of directly from the resource. | 07-07-2011 |
20110185136 | MOVING LARGE DYNAMIC DATASETS VIA INCREMENTAL CHANGE SYNCHRONIZATION - Incremental change synchronization for moving large data sets may be provided. Source data to be moved may be identified and a snapshot of the data may be created. The data may be moved to a new datastore and a second snapshot may be created. The snapshots may be compared to identify any data elements that have been modified and the modified elements may be copied to the new datastore. | 07-28-2011 |
20110185247 | MASSIVE STRUCTURED DATA TRANSFER OPTIMIZATIONS FOR HIGH-LATENCY, LOW-RELIABILITY NETWORKS - Optimizations for data transmission may be provided. A portion of a data block may be read into a batch by a read thread on a first server. The batch may be passed to a transmission thread. The transmission thread may then transmit the first batch to a second server while the read thread asynchronously reads a second portion of the data block into another batch. | 07-28-2011 |
20140379851 | AGGREGATING CONTENT FROM DIFFERENT CONTENT SOURCES AT A CLOUD SERVICE - A cloud service stores and aggregates content that is obtained from different content sources using different protocols. For example, the content may include electronic messages, calendar information, contacts, social network content, feed data, search results, and the like. The cloud service aggregates content for each user based on the user's configuration settings. The cloud service may perform processing on the aggregated content before it is delivered and displayed to the user on the client device. For example, one or more views may be generated and stored by the cloud service before the view is requested from the client. Changes made to the aggregated content on the client may be synchronized with the content source. Searches may be made across all or a portion of the different content sources that are aggregated for a user. | 12-25-2014 |