US 11,962,663 B1
Server-specified filters for long-lived client requests to fetch data in response to events
Richard Threlkeld, Seattle, WA (US); Yash H Patel, Redmond, WA (US); and Michael Paris, Seattle, WA (US)
Assigned to Amazon Technologies, Inc., Seattle, WA (US)
Filed by Amazon Technologies, Inc., Seattle, WA (US)
Filed on Mar. 17, 2022, as Appl. No. 17/697,777.
Int. Cl. G06F 15/16 (2006.01); G06F 9/54 (2006.01); G06F 16/242 (2019.01); G06F 16/2455 (2019.01); H04L 67/133 (2022.01); H04L 67/55 (2022.01)
CPC H04L 67/55 (2022.05) [G06F 9/542 (2013.01); G06F 16/2448 (2019.01); G06F 16/24568 (2019.01); H04L 67/133 (2022.05)] 20 Claims
OG exemplary drawing
 
1. 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.