US 11,962,663 B1 · Server-specified filters for long-lived client requests to fetch data in response to events

Abstract

Server-specified subscription filters for long-lived client requests to fetch data in response to events. In one aspect, the techniques encompass a method performed by a set of one or more computing devices. The method includes the step of receiving a long-lived request to fetch data in response to events sent by a client computing device. The method further includes receiving a server-specified subscription filter for the long-lived request and executing the long-lived request. Executing the long-lived request includes creating a persistent function that uses the server-specified subscription filter to map a source event stream to a response event stream. The response event stream is provided to the client computing device. The server-specified subscription filter facilitates filtering of events fetched for the long-lived request in a way that may not be possible or impractical if the subscription client were required to specify the filter in the long-lived request.

Claims20

Dependent claims

A method comprising:

receiving a GraphQL request, the GraphQL request comprising a subscription operation, the subscription operation referencing a subscription field within a selection set, the GraphQL request sent by a subscription client;
receiving a server-specified filter for the subscription operation;
wherein the server-specified filter comprises one or more predicates;
wherein at least one field, operator, or value of at least one predicate of the one or more predicates originates at a server as opposed to the subscription client;
executing the subscription operation including creating a persistent function for the subscription field that uses the server-specified filter to map a source event stream to a response event stream for the subscription client;
mapping the source event stream to the response event stream for the subscription client using the server-specified filter;
and
providing events from the source event stream that are mapped to the response event stream for the subscription client to the subscription client via a bi-directional data communications channel established with the subscription client.

5 more elements

A system comprising:

a first one or more computing devices to implement a long-lived connection service, the long-lived connection service comprising instructions which when executed cause the long-lived connection service to:
receive an application programming interface (API) query language long-lived request to fetch data in response to events, wherein the API query language long-lived request is to be sent by a subscription client, wherein the API query language long-lived request is to not comprise a client-specified subscription filter or is to comprise a partially-specified client-specified subscription filter;
create a persistent function that is programmed or configured to use a server-specified filter to map a source event stream to a response event stream, wherein the server-specified filter is to comprise one or more predicates, wherein at least one field, operator, or value of at least one predicate of the one or more predicates is to originate at a server as opposed to the subscription client, and
map the source event stream to the response event stream using the server-specified filter;
and
a second one or more computing devices to implement an application programming interface query language execution service, the execution service comprising instructions which when executed cause the execution service to execute the application programming interface (API) query language long-lived request including receive the server-specified filter.

3 more elements

Dependencies are inferred from the claim text.

Server-specified filters for long-lived client requests to fetch data in response to events

Life of this patent

Server-specified filters for long-lived client requests to fetch data in response to events

Life of this patent

Abstract

Claims20