Google Inc.

Amazon Technologies, Inc.

Munjal Doshi

Glen Murphy

Erik Kay

Antony John Sargent

Alexandra Levich

Zhenhai Lin

Rahul Roy-Chowdhury

Peter H Williamson

Rachit Jain

Ankit Kumar

Dmitry Titov

Xiaoyong Liu

Sandesh Sanjeev

Justin DeWitt

Jennifer Braithwaite

Sharad Sridhar

Daniel Cheng

Somas Thyagaraja

Features are disclosed for managing multiple hosts that stream sequential data to nodes for propagation. The hosts can include a primary host and a failover host that each store a replica of the sequential data. A computing device can monitor the hosts and identify the occurrence of a failover event for the primary host. For example, the computing device may determine the schema has been modified. The computing device can further determine to failover to the failover host based on the failover event. The computing device can insert a flip task into the stream of sequential data for the primary host. The insertion of the flip task may be automatic. Further, each node reading from the stream of sequential data for the primary host may encounter the flip task and failover to the failover host at the same logical position but a different absolute position.

Managing failover between data streams

A non-transitory computer-readable storage medium may comprise instructions stored thereon that, when executed by at least one processor, are configured to cause an intermediary server to at least receive, from a first client device, a first login request via a first browser installed on the first client device, the first login request identifying a user account, receive, from a third-party server, a message request, the message request including an identifier and indicating a browser application or a browser extension, map the identifier to the user account, determine whether the user account has installed the browser application or browser extension, and if the user account has installed the browser application or browser extension, send a first message to the first browser based on the message request.

Browser notifications

The disclosed subject matter relates to a system for messaging between applications, the system having one or more processors and a memory including instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including receiving a message including an identifier associated with a web application having a subscription to receive selected events associated with a publisher operating on a data network. The operations also include receiving, from the publisher, an event notification of at least one of the selected events. The operations also include determining whether the web application is subscribed to receive the event notification. The operations also include transmitting, in a case where the web application is subscribed to receive the event notification, an indication of the event notification to the web application.

Messaging between web applications

A system includes a memory configured to store executable code and a processor operably coupled to the memory. The processor is configured to execute the code to receive a request from a developer of a first web application to provide a notification corresponding to the first web application, authenticate the developer using a client identifier, after authenticating the developer, receive a content of the notification and a first user identifier, and provide the content of the notification to at least one of a plurality of computing devices associated with the first user identifier, based on an account associated with the first user identifier. The system syncs the notification and a plurality of computing devices associated with the first user identifier, based on the account.

Push notifications for web applications and browser extensions

A system for secure delegated authentication for applications may include one or more processors and a memory. The one or more processors perform operations including receiving a request from an application to retrieve a user authorization associated with a service provider. The operations also include authenticating the application in response to the request, the application being assigned a first identifier to associate the request with the application. The operations also include communicating the request to the service provider upon the application being authenticated. The operations also include receiving a response from the service provider, the response identifying a particular application associated with the service provider. The operations also include comparing the first identifier with at least a portion of the response to determine a match. The operations further include forwarding the received response to the application if a match is determined.

Secure delegated authentication for applications

A system includes a memory configured to store executable code and a processor operably coupled to the memory. The processor is configured to execute the code to receive a request from a developer of a first web application to provide a notification corresponding to the first web application, authenticate the developer using a client identifier, after authenticating the developer, receive a content of the notification and a first user identifier, and provide the content of the notification to at least one of a plurality of computing devices associated with the first user identifier, based on an account associated with the first user identifier.

Growing community of inventors

Sammamish, WA, United States of America

Munjal Doshi