Abstract: Security policy update supporting at least one security service provider includes each of one or more security service providers receiving a set of new rules to be enforced as part of a new security policy. Each security service provider processes the new rules in order to be ready to begin using the new rules, but continues to use the previous set of rules until instructed to begin using the new rules. When all of the one or more security service providers are ready to begin using the new rules, they are instructed to begin using the new rules at which point all of the security service providers begin using the set of new rules substantially concurrently.

Abstract: Page-view recording with click-thru tracking is described. In an embodiment, a tracking system receives a request for content that includes request-tracking information. The request-tracking information designates that the tracking system receive the content request before the request is communicated to a content provider. The request for content is communicated to the content provider that provides the content. The content includes content-tracking information that the tracking system receives from a requesting device when the content is provided to the requesting device. The tracking system maintains the request-tracking and the content-tracking information, and associates the request-tracking and the content-tracking information with the destination device.

Abstract: Page-view recording with click-thru tracking is described. In an embodiment, a tracking system receives a request for content that includes request-tracking information. The request-tracking information designates that the tracking system receive the content request before the request is communicated to a content provider. The request for content is communicated to the content provider that provides the content. The content includes content-tracking information that the tracking system receives from a requesting device when the content is provided to the requesting device. The tracking system maintains the request-tracking and the content-tracking information, and associates the request-tracking and the content-tracking information with the destination device.

Abstract: An event, such as a security-related event, is received from a first security engine or another source. A second security engine is identified that is configured to utilize information contained in the event. The information contained in the event is then communicated to the second security engine. Additionally, other information, such as system state information, can be provided to one or more security engines.

Abstract: Individual records of a data set include data and semantic information to describe the data. The records in the data set are encoded to generate an encoded data set using a compression function which is determined from semantic information that is common to multiple records of the data set. Multiple records of the encoded data set include the data without the common semantic information. The encoded data set is transmitted, or otherwise communicated, to a destination device along with an expansion function that includes the semantic information that is common to the multiple records of the data set. The destination device expands the encoded data set with the expansion function such that the multiple records of the encoded data set are expanded to include the common semantic information.

Abstract: A tracking system receives a request for content that includes request-tracking information. The request-tracking information includes identifiers for the content, a content provider, a destination device for the content, a selectable data link that generates the request, rendered content that includes the data link, and a location of the data link within the rendered content. The request-tracking information designates that the tracking system receive the content request before the request is communicated to the content provider. The request for content is communicated to the content provider that provides the content. The content includes content-tracking information having identifiers for the content provider, the destination device, and the content. The tracking system receives the content-tracking information from the destination device when the content is provided to the destination device.

Abstract: A tracking system receives a request for content that includes request-tracking information. The request-tracking information includes identifiers for the content, a content provider, a destination device for the content, a selectable data link that generates the request, rendered content that includes the data link, and a location of the data link within the rendered content. The request-tracking information designates that the tracking system receive the content request before the request is communicated to the content provider. The request for content is communicated to the content provider that provides the content. The content includes content-tracking information having identifiers for the content provider, the destination device, and the content. The tracking system receives the content-tracking information from the destination device when the content is provided to the destination device.

Abstract: A system and method for incremental change synchronization among multiple copies of data is disclosed. To achieve the synchronization a genera synchronization model is used. The synchronization model establishes a one-way data flow path to allow incremental changes to be transferred from a copy of data that incorporates the incremental changes to a copy of data that does not yet incorporate the incremental changes. To achieve this one-way data flow path, the synchronization model uses an agent, a data collector, and a data synchronizer. The data collector collects incremental changes transferred to it and applies the incremental changes to a copy of data. A data synchronizer transfers incremental changes to a data collector. An agent controls the synchronization process by making a connection between a data collector and a data synchronizer and then directing the data synchronizer to transfer data to the data collector.

Abstract: In an electronic mail system comprising a local computer that can be connected to a message server over a data link, mechanisms are provided to convert large identification codes used by the message server to store and access messages and folders into shorter identification codes used by the local computer to access locally stored copies of the messages or folders. The large server identification codes, including a 46-byte folder codes and 70-byte message codes, are converted using a conversion technique that operates in one of two modes, depending on whether the data link to a master conversion map on the message server is available and operative. In the first mode, to convert the codes to 8-byte codes, the technique uses a local cache that retains mapping information produced in conversions using the master conversion map. In the second mode, three types of local maps are implemented as B-trees are used to convert the codes first to the 8-byte codes and then to 4-byte codes.