Abstract: A thread delta prediction and cognitive conversation opportunity generation. A prediction model may be generated based on chat space conversation data, and predicts a chat thread delta associated with a current chat conversation data. A data package may be created based on the chat thread delta. Based on the data package, a conversation opportunity may be determined for a given topic for given user in the chat space, to conduct during a time period of the chat thread delta in real-time.

Abstract: Embodiments of the present invention provide systems and methods for self-certification by a developer that the software components used during development are used in a secure manner, through the use of annotations. Input and return conditions are defined in an annotation for the software components of a system. The input and return conditions are compared for a match and a warning is generated when the input and return conditions do not match.

Abstract: Embodiments of the present invention provide systems and methods for self-certification by a developer that the software components used during development are used in a secure manner, through the use of annotations. Input and return conditions are defined in an annotation for the software components of a system. The input and return conditions are compared for a match and a warning is generated when the input and return conditions do not match.

Abstract: A thread delta prediction and cognitive conversation opportunity generation. A prediction model may be generated based on chat space conversation data, and predicts a chat thread delta associated with a current chat conversation data. A data package may be created based on the chat thread delta. Based on the data package, a conversation opportunity may be determined for a given topic for given user in the chat space, to conduct during a time period of the chat thread delta in real-time.

Abstract: Embodiments of the present invention provide systems and methods for self-certification by a developer that the software components used during development are used in a secure manner, through the use of annotations. Input and return conditions are defined in an annotation for the software components of a system. The input and return conditions are compared for a match and a warning is generated when the input and return conditions do not match.

Abstract: Embodiments of the present invention provide systems and methods for self-certification by a developer that the software components used during development are used in a secure manner, through the use of annotations. Input and return conditions are defined in an annotation for the software components of a system. The input and return conditions are compared for a match and a warning is generated when the input and return conditions do not match.

Abstract: Methods for message synchronization are described herein. The methods include establishing, via a message server, a communication channel session between a first client of a first user and a second client among a plurality of clients of a second user. The second client is designated as a primary client among the plurality of clients of a second user during the session, and a message to be exchanged between the first client and the second client via the message server is enabled. The methods may also include providing, from the message server, message history associated with the session to a message history data store comprising a computing device that is discrete from the message server. The message history may be provided to a third client among the plurality of clients of the second user via the message history data store, rather than the message server.

Abstract: Methods for message synchronization are described herein. The methods include establishing, via a message server, a communication channel session between a first client of a first user and a second client among a plurality of clients of a second user. The second client is designated as a primary client among the plurality of clients of a second user during the session, and a message to be exchanged between the first client and the second client via the message server is enabled. The methods may also include providing, from the message server, message history associated with the session to a message history data store comprising a computing device that is discrete from the message server. The message history may be provided to a third client among the plurality of clients of the second user via the message history data store, rather than the message server.

Abstract: A method, software tool and system for communicating data between components in a client computer system is provided. The client computer system has a user interface for displaying a page comprising content rendered by a plurality of components. A property broker is provided which maintains a registry of linked source and destination data fields of components of the client computer system. The property broker is notified when a user request is detected by a component registered with the property broker, and a set of components registered with the property broker is then notified of the start of a communication phase. The user request is processed by the actioned component and the value of each source data field updated during processing of the user request is communicated to each component having a linked destination data field. The property broker notifies the set of components when the communications phase has ended, and at least one component then renders content for display.