Abstract: Implementations are described which provide for recipient-based filtering of an event that relates to a topic to which consumers are subscribed. Responsive to determining that an attribute of the event includes a set of one or more identifiers for intended recipients for the event, the event is delivered to consumers that correspond to the intended recipients. Alternatively, responsive to determining that the attribute of the event does not include a set of one or more identifiers for intended recipients for the event, the event is delivered to all of the consumers subscribed to the topic to which the event relates.

Abstract: Described herein are a system, apparatus, device, method, and/or computer program product embodiments and/or combinations and sub-combinations thereof for displaying a live database record in a chat session. In a given embodiment, a collaborative communications system may cause display of a subset of fields the database record in a chat session. The collaborative communications system may detect activation of the chat session. The collaborative communications system may retrieve the current values of the subset of fields. Upon retrieval, the collaborative communications system causes display of the subset of fields of the database record including an updated value for a field in the chat session.

Abstract: Implementations are described for selectively publishing an event responsive to an operation on a database in a transaction. Publishing the event is delayed or not delayed respectively, responsive to determining that a value of an attribute for the event indicates that publishing the event is to be delayed, or not to be delayed, until the transaction is rolled back or committed. If publishing the event is delayed, the event is published if the transaction is committed and discarded if the transaction is rolled back. If publishing the event is not delayed, the event is published. Optionally, if the event is published, the event is published in a database or a datastore respectively, responsive to determining whether another value of another attribute for the event indicates that the event is to be published in a database or a datastore.

Abstract: Described herein are a system, apparatus, device, method, and/or computer program product embodiments and/or combinations and sub-combinations thereof for displaying a live database record in a chat session. In a given embodiment, a collaborative communications system may cause display of a subset of fields the database record in a chat session. The collaborative communications system may detect activation of the chat session. The collaborative communications system may retrieve the current values of the subset of fields. Upon retrieval, the collaborative communications system causes display of the subset of fields of the database record including an updated value for a field in the chat session.

Abstract: Described herein are a system, apparatus, device, method, and/or computer program product embodiments and/or combinations and sub-combinations thereof for displaying a live database record in a chat session. In a given embodiment, a collaborative communications system may cause display of a subset of fields the database record in a chat session. The collaborative communications system may detect activation of the chat session. The collaborative communications system may retrieve the current values of the subset of fields. Upon retrieval, the collaborative communications system causes display of the subset of fields of the database record including an updated value for a field in the chat session.

Abstract: Implementations are described which provide for recipient-based filtering of an event that relates to a topic to which consumers are subscribed. Responsive to determining that an attribute of the event includes a set of one or more identifiers for intended recipients for the event, the event is delivered to consumers that correspond to the intended recipients. Alternatively, responsive to determining that the attribute of the event does not include a set of one or more identifiers for intended recipients for the event, the event is delivered to all of the consumers subscribed to the topic to which the event relates.

Abstract: Techniques and structures to manage a multi-channel client-server connection is disclosed. A connection session is established between a client and in server response to receiving a call from a first browser interface element to establish the connection session. The session is shared in response to receiving a second call from a second browser interface element to establish a connection session.

Abstract: Implementations are described which provide for recipient-based filtering of an event that relates to a topic to which consumers are subscribed. Responsive to determining that an attribute of the event includes a set of one or more identifiers for intended recipients for the event, the event is delivered to consumers that correspond to the intended recipients. Alternatively, responsive to determining that the attribute of the event does not include a set of one or more identifiers for intended recipients for the event, the event is delivered to all of the consumers subscribed to the topic to which the event relates.

Abstract: Implementations are described which provide for recipient-based filtering of an event that relates to a topic to which consumers are subscribed. Responsive to determining that an attribute of the event includes a set of one or more identifiers for intended recipients for the event, the event is delivered to consumers that correspond to the intended recipients. Alternatively, responsive to determining that the attribute of the event does not include a set of one or more identifiers for intended recipients for the event, the event is delivered to all of the consumers subscribed to the topic to which the event relates.

Abstract: Implementations are described for selectively publishing an event responsive to an operation on a database in a transaction. Publishing the event is delayed or not delayed respectively, responsive to determining that a value of an attribute for the event indicates that publishing the event is to be delayed, or not to be delayed, until the transaction is rolled back or committed. If publishing the event is delayed, the event is published if the transaction is committed and discarded if the transaction is rolled back. If publishing the event is not delayed, the event is published. Optionally, if the event is published, the event is published in a database or a datastore respectively, responsive to determining whether another value of another attribute for the event indicates that the event is to be published in a database or a datastore.

Abstract: Techniques and structures to manage a multi-channel client-server connection is disclosed. A connection session is established between a client and in server response to receiving a call from a first browser interface element to establish the connection session. The session is shared in response to receiving a second call from a second browser interface element to establish a connection session.

Abstract: Implementations are described which provide for recipient-based filtering of an event that relates to a topic to which consumers are subscribed. Responsive to determining that an attribute of the event includes a set of one or more identifiers for intended recipients for the event, the event is delivered to consumers that correspond to the intended recipients. Alternatively, responsive to determining that the attribute of the event does not include a set of one or more identifiers for intended recipients for the event, the event is delivered to all of the consumers subscribed to the topic to which the event relates.

Abstract: A method and system for event delivery are described. A batch of events for a first topic with replay identifiers is received. Responsive to determining that there is an active replay identifier discontinuity information for the first topic, a determination is performed of whether the first batch of events includes a second set of events that fills the discontinuity identified in the replay identifier discontinuity information. Upon determining that the first batch of events includes a second subset of events with second respective replay identifiers that start from the last replay identifier and do not include a discontinuity the second subset of events is transmitted to an event consumer, and the replay identifier discontinuity information for the first topic is updated based on the second subset of events transmitted.

Abstract: A method and system for event delivery are described. A batch of events for a first topic with replay identifiers is received. Responsive to determining that there is an active replay identifier discontinuity information for the first topic, a determination is performed of whether the first batch of events includes a second set of events that fills the discontinuity identified in the replay identifier discontinuity information. Upon determining that the first batch of events includes a second subset of events with second respective replay identifiers that start from the last replay identifier and do not include a discontinuity the second subset of events is transmitted to an event consumer, and the replay identifier discontinuity information for the first topic is updated based on the second subset of events transmitted.