# US 2019/0379650 A1 · Reactive programming subscription context

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0379650 A1
- Document ID: US20190379650A1
- Status: Published application
- Kind: A1
- Application number: 16/377,017
- Filed: 2019-04-05
- Published: 2019-12-12
- Earliest claimed: 2018-06-08
- Assignees: Pivotal Software, Inc.
- Applicants: Pivotal Software, Inc.
- Inventors: Joseph Benjamin Hale; Stéphane Adrien Joseph Maldini; Simon Baslé
- Web page: https://patentgrep.com/patent/US20190379650A1

## CPC

- G06F 21/31: User authentication
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 67/562: Brokering proxy services
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for implementing subscription contexts in a reactive programming system. One of the methods includes receiving, by a reactive programming system comprising one or more computers, a reactive programming program defining an ordering of a plurality of operators, the plurality of operators including a subscriber context operator that writes a value to a subscription context for a particular subscriber, wherein the ordering defines an upstream subscription flow ordering from the particular subscriber to a publisher and a downstream data flow ordering from the publisher to the particular subscriber. The operators are evaluated in the upstream subscription flow ordering, including updating a subscription context of each operator with the value written by the subscriber context operator.

## Claims

### Claim 1

A reactive programming system comprising:
one or more computers and one or more storage devices storing instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising:
receiving a reactive programming program defining an ordering of a plurality of operators, the plurality of operators including a subscriber context operator that writes a value to a subscription context for a particular subscriber, wherein the ordering defines an upstream subscription flow ordering from the particular subscriber to a publisher and a downstream data flow ordering from the publisher to the particular subscriber;
evaluating the operators in the upstream subscription flow ordering, including updating a subscription context of each operator with the value written by the subscriber context operator; and
upon receiving an input data item, processing the input data item using the operators in the downstream data flow ordering to generate a final output data item for the input data item, wherein one or more operators that are executed in the downstream data flow ordering access the value of the subscription context written by the subscriber context operator during evaluation of the operations in the upstream subscription flow ordering.

### Claim 2 (depends on 1)

The system of claim 1, wherein the subscriber context operator occurs in the program after one or more other operators but is executed before any of the other operators.

### Claim 3 (depends on 1)

The system of claim 1, wherein evaluating the operators in the upstream subscription flow ordering propagates the subscription context from the particular subscriber to the publisher.

### Claim 4 (depends on 1)

The system of claim 1, wherein one or more of the operators are executed by different threads of the reactive programming system.

### Claim 5 (depends on 1)

The system of claim 1, wherein the plurality of operators include a second subscriber context operator that is upstream from the subscriber context operator, and wherein updating the subscription context for the second subscriber context operator comprises merging a second value written by the second subscriber context with the value written by the subscriber context operator.

### Claim 6 (depends on 1)

The system of claim 1, wherein the value written by the subscriber context operator is only available to operators that are upstream from the subscriber context operator.

### Claim 7 (depends on 1)

The system of claim 1, wherein accessing, by a particular operator, the value of the subscription context comprises requesting the value of the subscription context from another operator downstream from the particular operator.

### Claim 8 (depends on 1)

The system of claim 1, wherein the subscription context is immutable while processing the input data item using the operators in the downstream data flow.

### Claim 9 (depends on 1)

The system of claim 1, wherein a second subscriber context operator that is upstream from the subscriber context operator writes a second value that masks the value written by the subscriber context operator by making a copy of the subscription context having the second value.

### Claim 10 (depends on 1)

The system of claim 1, wherein a nested value, written by a nested subscriber context operator that is nested inside a first operator of the plurality of operators, is not visible to any upstream operators of the first operator.

### Claim 11

A computer-implemented method comprising:
receiving, by a reactive programming system comprising one or more computers, a reactive programming program defining an ordering of a plurality of operators, the plurality of operators including a subscriber context operator that writes a value to a subscription context for a particular subscriber, wherein the ordering defines an upstream subscription flow ordering from the particular subscriber to a publisher and a downstream data flow ordering from the publisher to the particular subscriber;
evaluating, by the reactive programming system, the operators in the upstream subscription flow ordering, including updating a subscription context of each operator with the value written by the subscriber context operator; and
upon receiving an input data item, processing, by the reactive programming system, the input data item using the operators in the downstream data flow ordering to generate a final output data item for the input data item, wherein one or more operators that are executed in the downstream data flow ordering access the value of the subscription context written by the subscriber context operator during evaluation of the operations in the upstream subscription flow ordering.

### Claim 12 (depends on 11)

The method of claim 11, wherein the subscriber context operator occurs in the program after one or more other operators but is executed before any of the other operators.

### Claim 13 (depends on 11)

The method of claim 11, wherein evaluating the operators in the upstream subscription flow ordering propagates the subscription context from the particular subscriber to the publisher.

### Claim 14 (depends on 11)

The method of claim 11, wherein one or more of the operators are executed by different threads of the reactive programming system.

### Claim 15 (depends on 11)

The method of claim 11, wherein the plurality of operators include a second subscriber context operator that is upstream from the subscriber context operator, and wherein updating the subscription context for the second subscriber context operator comprises merging a second value written by the second subscriber context with the value written by the subscriber context operator.

### Claim 16 (depends on 11)

The method of claim 11, wherein the value written by the subscriber context operator is only available to operators that are upstream from the subscriber context operator.

### Claim 17 (depends on 11)

The method of claim 11, wherein accessing, by a particular operator, the value of the subscription context comprises requesting the value of the subscription context from another operator downstream from the particular operator.

### Claim 18 (depends on 11)

The method of claim 11, wherein the subscription context is immutable while processing the input data item using the operators in the downstream data flow.

### Claim 19 (depends on 11)

The method of claim 11, wherein a second subscriber context operator that is upstream from the subscriber context operator writes a second value that masks the value written by the subscriber context operator by making a copy of the subscription context having the second value.

### Claim 20 (depends on 11)

The method of claim 11, wherein a nested value, written by a nested subscriber context operator that is nested inside a first operator of the plurality of operators, is not visible to any upstream operators of the first operator.

### Claim 21

A computer program product, encoded on one or more non-transitory computer storage media, comprising instructions that when executed by one or more computers of a reactive programming system cause the one or more computers to perform operations comprising:
receiving a reactive programming program defining an ordering of a plurality of operators, the plurality of operators including a subscriber context operator that writes a value to a subscription context for a particular subscriber, wherein the ordering defines an upstream subscription flow ordering from the particular subscriber to a publisher and a downstream data flow ordering from the publisher to the particular subscriber;
evaluating the operators in the upstream subscription flow ordering, including updating a subscription context of each operator with the value written by the subscriber context operator; and
upon receiving an input data item, processing the input data item using the operators in the downstream data flow ordering to generate a final output data item for the input data item, wherein one or more operators that are executed in the downstream data flow ordering access the value of the subscription context written by the subscriber context operator during evaluation of the operations in the upstream subscription flow ordering.
