Abstract: Techniques for message deduplication are described. In one embodiment, an apparatus may comprise a client front-end component operative to receive an incoming message at a messaging system from a messaging client on a client device; extract a deduplication token from the incoming message; store the incoming message in a message queue where examining the deduplication token determines that the incoming message does not duplicate any existing message of the messaging system; and discard the incoming message where examining the deduplication token determines that the incoming message does duplicate an existing message; and a message deduplication component operative to examine the deduplication token to determine whether the incoming message duplicates any existing message of the messaging system. Other embodiments are described and claimed.

Abstract: Techniques for ephemeral message are described. In one embodiment, an apparatus may comprise a delayed-action worker module operative to wake according to a wake timer; determine a current update object for a delayed-action cursor for a recipient update queue for a messaging system, the delayed-action cursor associated with an action delay for the recipient update queue; determine a delayed-action activity for the current update object; perform the delay-action activity for the current update object; determine a next update object for the delayed-action cursor for the recipient update queue; and determine a next wake timer for the delayed-action worker module based on the action delay and a creation time for the next update object. Other embodiments are described and claimed.

Abstract: Techniques for directive-based messaging synchronization are described. In one embodiment, an apparatus may comprise a local network component operative to receive a directive package at a messaging client on a client device; and a local database synchronization component operative to execute the directive package with a messaging-sync virtual machine to modify a local messaging database of the messaging client; and refresh a user interface component of the messaging client in response to modifying the local messaging database of the messaging client. Other embodiments are described and claimed.

Abstract: Techniques for intelligent messaging for message syncing are described. An apparatus may comprise a recipient inbound messaging component, a recipient queue management component, a recipient update customization component, and a recipient outbound messaging component. The recipient inbound messaging component may be operative to receive an incoming update at a recipient update queue, the recipient update queue associated with a recipient of the incoming update. The recipient queue management component may be operative to add the incoming update to the recipient update queue and determine a recipient messaging endpoint to receive the incoming update. The recipient update customization component may be operative to retrieve one or more recipient messaging endpoint parameters associated with the recipient messaging endpoint and generate a customized incoming update from the incoming update according to the one or more recipient messaging endpoint parameters.

Abstract: Techniques for a database-driven messaging user interface are described. In one embodiment, an apparatus may comprise a database access component operative to determine that a local messaging database of a messaging client on a client device has been updated; and examine the local messaging database to determine a set of database queries to rerun for a plurality of local user interface components; and the local user interface components operative to refresh based on running the set of database queries against the local messaging database. Other embodiments are described and claimed.

Abstract: Techniques for backend-specific cursor tracking are described. In one embodiment, an apparatus may comprise a local database synchronization component operative to initiate a client update at a messaging client on a client device, the client update associated with a specific backend service for a messaging system; retrieve an opaque backend-specific update cursor for the specific backend service; and store an updated opaque backend-specific update cursor for the messaging client; and a local network component operative to send the opaque backend-specific update cursor to the messaging system in association with a client update request; and receive an update package at the messaging client on the client device, the update package comprising the updated opaque backend-specific update cursor. Other embodiments are described and claimed.

Abstract: Techniques for directive-based messaging synchronization are described. In one embodiment, an apparatus may comprise a local network component operative to receive a directive package at a messaging client on a client device; and a local database synchronization component operative to execute the directive package with a messaging-sync virtual machine to modify a local messaging database of the messaging client; and refresh a user interface component of the messaging client in response to modifying the local messaging database of the messaging client. Other embodiments are described and claimed.

Abstract: Techniques for in-place directive execution are described. In one embodiment, an apparatus may comprise a local network component operative to receive a directive package at a messaging client on a client device, the directive package formatted according to a serialized directive schema; and store the directive package in a memory of the client device in the serialized directive schema; and a local database synchronization component operative to execute the directive package using in-place access of the directive package in the memory of the client device. Other embodiments are described and claimed.

Abstract: The present disclosure relates to systems, methods, and devices for sending and receiving payments using an integrated payment and messaging system. In particular, the integrated payment and messaging system allows users to send and receive electronic payments as well as exchange messages. For example, one or more implementations involve facilitating message exchanges and payment transactions using push notifications via separate message and payment queues. To illustrate, one or more implementations involve pushing status updates to a payment transaction using a payment queue specific to a user. Additionally, one or more implementations involve associating payment transactions with messages within a messaging thread for providing updates to each user in the messaging thread.

Abstract: Techniques for message indexing are described. In one embodiment, an apparatus may comprise a client front-end component operative to receive an incoming message from a client device at a client front-end component for a messaging system; and extract a message identifier for the incoming message from the incoming message, wherein the message identifier uniquely identifies the incoming message; and a message queue operative to store the incoming message in a message storage system based on indexing the incoming message based on the message identifier. Other embodiments are described and claimed.

Abstract: Techniques for message deduplication are described. In one embodiment, an apparatus may comprise a client front-end component operative to receive an incoming message at a messaging system from a messaging client on a client device; extract a deduplication token from the incoming message; store the incoming message in a message queue where examining the deduplication token determines that the incoming message does not duplicate any existing message of the messaging system; and discard the incoming message where examining the deduplication token determines that the incoming message does duplicate an existing message; and a message deduplication component operative to examine the deduplication token to determine whether the incoming message duplicates any existing message of the messaging system. Other embodiments are described and claimed.

Abstract: Techniques for messaging conversation indexing are described. In one embodiment, an apparatus may comprise a client front-end component operative to receive an incoming message from a client device at a client front-end component for a messaging system; and extract a messaging conversation identifier for a messaging conversation from the incoming message, wherein the messaging conversation identifier uniquely identifies the messaging conversation for the incoming message, wherein the incoming message is one of a plurality of messaging conversation messages for the messaging conversation; and a message queue operative to store the incoming message in a message storage system based on indexing the incoming message with the messaging conversation identifier. Other embodiments are described and claimed.

Abstract: The disclosure is directed to pushing data updates to client computing devices (“clients”) in real-time. Clients can obtain data from a data storage layer by sending queries to the data storage layer that will return data compatible with the client's local data model. These queries are stored in a database and the identifier for the query (“query ID”) is used instead of the query itself. In the query stored in the database, a marker is used as a proxy for a content ID of the content to be retrieved. When querying, both the query ID and the content ID are passed to the data storage layer. The query stored with the query id is loaded, the marker is substituted with the content ID, and then executed.

Abstract: The disclosure is directed to pushing data updates to client computing devices (“clients”) in real-time. Clients can obtain data from a data storage layer by sending queries to the data storage layer that will return data compatible with the client's local data model. These queries are stored in a database and the identifier for the query (“query ID”) is used instead of the query itself. In the query stored in the database, a marker is used as a proxy for a content ID of the content to be retrieved. When querying, both the query ID and the content ID are passed to the data storage layer. The query stored with the query id is loaded, the marker is substituted with the content ID, and then executed.

Abstract: The present disclosure relates to systems, methods, and devices for sending and receiving payments using an integrated payment and messaging system. In particular, the integrated payment and messaging system allows users to send and receive electronic payments as well as exchange messages. For example, one or more implementations involve facilitating message exchanges and payment transactions using push notifications via separate message and payment queues. To illustrate, one or more implementations involve pushing status updates to a payment transaction using a payment queue specific to a user. Additionally, one or more implementations involve associating payment transactions with messages within a messaging thread for providing updates to each user in the messaging thread.

Abstract: Techniques for a sequential message reader for message syncing are described. An apparatus may comprise a network component and an inbox management component. The network component may be operative to receiving an incoming update at a messaging endpoint from a recipient update queue, the incoming update comprising an incoming recipient sequence number. The inbox management component may be operative to add the incoming update to a message inbox on the messaging endpoint, the incoming update added to the message inbox in an order determined by the incoming recipient sequence number and determine based on the incoming recipient sequence number whether one or more additional updates are missing from the message inbox on the messaging endpoint. Other embodiments are described and claimed.

Abstract: Techniques for intelligent messaging for message syncing are described. An apparatus may comprise a recipient inbound messaging component, a recipient queue management component, a recipient update customization component, and a recipient outbound messaging component. The recipient inbound messaging component may be operative to receive an incoming update at a recipient update queue, the recipient update queue associated with a recipient of the incoming update. The recipient queue management component may be operative to add the incoming update to the recipient update queue and determine a recipient messaging endpoint to receive the incoming update. The recipient update customization component may be operative to retrieve one or more recipient messaging endpoint parameters associated with the recipient messaging endpoint and generate a customized incoming update from the incoming update according to the one or more recipient messaging endpoint parameters.

Abstract: Techniques for a persistent queue for message syncing are described. A recipient inbound messaging component may receive an incoming update at a recipient update queue. A recipient queue management component may determine an incoming recipient sequence number for the recipient update queue. A recipient outbound messaging component may transmit the incoming update to the recipient messaging endpoint. Other embodiments are described and claimed.