Salesforce Com, Inc.

Salesforce, Inc.

Vikram Kommaraju

Soumen Bandyopadhyay

John Arlan Brock

Lawrence Eugenio McAlpin

Sivananda Reddy Thummala Abbigari

Alexey Syomichev

Jay Hurst

Purushotham Babu Naidu

Pulkit Mehta

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.

Recipient-based filtering in a publish-subscribe messaging system

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.

Selectively publishing an event responsive to an operation on a database in a transaction which is rolled back or committed

Implementations store an event associated with a topic in a database to allow for the event to be transmitted in order with respect to other events associated with the topic which are stored in the database. A commit of a transaction is performed that includes inserting the event's payload in a record in a database object. After the commit, a field for the record is updated with an identifier of the commit. The identifier and identifiers of other commits of other transactions on the database indicate ordering of the commit with respect to the other commits. Another field of another record is updated based on the identifier and a last stored value such that the payloads of the event and of the other events are retrievable to be transmitted in an order based on the value of the other field and values of other fields of other records.

Event ordering based on an identifier for a transaction

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.

Growing community of inventors

Dublin, CA, United States of America

Vikram Kommaraju