Abstract: Sensor-based shaving systems and methods of analyzing a user's shave event are described for determining a unique threshold value of the user. A grooming device comprises a handle having a connecting structure connected to a hair cutting implement. A shave event sensor associated with the grooming device measures a user behavior, which includes collecting a first dataset comprising shave data defining a shave event. The first dataset is transmitted via a communication device and is analyzed to determine baseline behavior data of the user, and a unique threshold value of the user is determined from the baseline behavior data. One or more subsequent datasets, each comprising shave data of one or more corresponding shave events, is compared to the unique threshold value to determine comparison data. An indication is provided, based on the comparison data, to indicate a deviation from the threshold value and to influence the user behavior.

Abstract: Sensor-based shaving systems and methods of analyzing a user's shave event are described for determining a unique threshold value of the user. A grooming device comprises a handle having a connecting structure connected to a hair cutting implement. A shave event sensor associated with the grooming device measures a user behavior, which includes collecting a first dataset comprising shave data defining a shave event. The first dataset is transmitted via a communication device and is analyzed to determine baseline behavior data of the user, and a unique threshold value of the user is determined from the baseline behavior data. One or more subsequent datasets, each comprising shave data of one or more corresponding shave events, is compared to the unique threshold value to determine comparison data. An indication is provided, based on the comparison data, to indicate a deviation from the threshold value and to influence the user behavior.

Abstract: The present invention relates to a method of manufacturing personalized razor handles.

Abstract: The present invention relates to a method of manufacturing personalized razor handles.

Abstract: A system, method, and computer program product are provided for detecting unwanted data based on an analysis of an icon. In use, an icon is analyzed. Furthermore, unwanted data is detected based on the analysis.

Abstract: A system, method, and computer program product are provided for detecting unwanted data based on an analysis of an icon. In use, an icon is analyzed. Furthermore, unwanted data is detected based on the analysis.

Abstract: A system, method, and computer program product are provided for verifying an identification of program information as unwanted. In use, program information is identified as unwanted at a client. Furthermore, the identification of the program information as unwanted is verified, utilizing a communication between the client and a server.

Abstract: A system, method, and computer program product are provided for detecting unwanted data based on an analysis of an icon. In use, an icon is analyzed. Furthermore, unwanted data is detected based on the analysis.

Abstract: A system, method, and computer program product are provided for verifying an identification of program information as unwanted. In use, program information is identified as unwanted at a client. Furthermore, the identification of the program information as unwanted is verified, utilizing a communication between the client and a server.

Abstract: A naming system, method and computer program product are provided. In use, unwanted code including at least one attribute is identified. In addition, an encoded name is generated for the unwanted code, where at least a portion of the encoded name represents the at least one attribute of the unwanted code.

Abstract: A source computer 8 stores updated data that is to be distributed to a plurality of destination computers (12 to 30). The destination computers (12 to 30) are divided into groups sharing a common priority level (5, 4, 3, 2, 1). Each of these groups is then associated with a push update task to be executed by the source computer 8. These push update tasks are then sequentially executed. If a particular group of destination computers exceeds a threshold size, then it may be further divided in accordance with a hierarchy of splitting rules. The push update tasks use multicasting to transfer the update data to the destination computers within their groups in a manner that reduces network traffic.

Abstract: In a malware scanner containing an updating program 20, a malware scanner engine 22 and malware definition data 24, the malware scanner engine 22 and the malware definition data 24 cross-check each other for validity. More particularly, each includes its own signature 26, 30 as well as public key information 28, 32 for checking the other. There is no dependence upon the updating software 20 for information required in the validating of the malware scanner engine 22 or malware definition data 24. The malware definition data 24 can include program code operable to utilize the validating data 32 embedded within the malware definition data 24 for checking the signature 26 of the malware scanner engine 22.

Abstract: A source computer 8 stores updated data that is to be distributed to a plurality of destination computers (12 to 30). The destination computers (12 to 30) are divided into groups sharing a common priority level (5, 4, 3, 2, 1). Each of these groups is then associated with a push update task to be executed by the source computer 8. These push update tasks are then sequentially executed. If a particular group of destination computers exceeds a threshold size, then it may be further divided in accordance with a hierarchy of splitting rules. The push update tasks use multicasting to transfer the update data to the destination computers within their groups in a manner that reduces network traffic.

Abstract: A malware protection mechanism is described whereby upon detection of an item of malware or malware like behaviour, I/O devices (18, 20, 22) of a computer (4, 6, 8, 10) may be disabled in order to resist propagation of the malware or infection by the malware. Alternatively, a System Administrator may manually trigger the disablement of the I/O devices as a pre-emptive precaution against infection.