Systems and methods for configuration of sequence handlers

Patent metadata

Field	Value
Publication number	US-11726934-B2
Application number	US-202217822525-A
Country	US
Kind code	B2
Filing date	Aug 26, 2022
Priority date	Sep 8, 2021
Publication date	Aug 15, 2023
Grant date	Aug 15, 2023

Abstract

A method for registering a handler in a configured sequence of handlers includes: receiving, by a processor and memory implementing a sequencer infrastructure, a configuration script defining a sequence including one or more handler identifiers and corresponding one or more handler arguments; invoking a handler initialization entry point for a handler corresponding to a handler identifier, the invoking the handler initialization entry point including: selecting, based on the corresponding one or more handler arguments, a handler type from among two or more of: a configured instance of the handler; a configured alternate handler different from the handler; an alternate sequence of handlers; an expression; and a no-op handler; and initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments; and adding the configured handler to a configured sequence of handlers.

First claim

What is claimed is:

1. A method for registering a handler in a configured sequence of handlers, the method comprising:
receiving, by a processor and memory storing instructions implementing a sequencer infrastructure, a configuration script defining a sequence comprising one or more handler identifiers and corresponding one or more handler arguments;
invoking, by the processor, a handler initialization entry point for a handler corresponding to a handler identifier of the one or more handler identifiers, the invoking the handler initialization entry point comprising:
selecting, based on the corresponding one or more handler arguments, a handler type from among two or more of:
a configured instance of the handler;
a configured alternate handler different from the handler;
an alternate sequence of handlers;
an expression; and
a no-op (no-operation) handler; and

initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments;

adding, by the processor, the configured handler to a configured sequence of handlers; and
executing, by a sequencer of the sequencer infrastructure, the configured sequence of handlers to generate an output in response to an input.

2. The method of claim 1 , wherein the selecting the handler type is further based on a plurality of parameters of an execution environment of the sequencer.

3. The method of claim 2 , wherein the parameters of the execution environment comprise:
a version number of the sequencer infrastructure;
a handler registry of handlers available to the sequencer infrastructure;
a plurality version numbers of corresponding ones of the handlers of the handler registry;
descriptions of hardware capabilities of a server comprising the processor and memory and configured to execute the sequencer; or
a location of the server.

4. The method of claim 2 , wherein the invoking the handler initialization entry point further comprises dynamically registering the handler with the execution environment.

5. The method of claim 4 , wherein the handler is retrieved from a remote source over a network.

6. The method of claim 1 , wherein the sequencer executing the configured sequence of handlers processes requests and generates responses in a content delivery network.

7. The method of claim 1 , wherein the sequencer executing the configured sequence of handlers processes requests and generates responses in a web application server.

8. The method of claim 1 , wherein the sequencer processes input data in a stream processing pipeline corresponding to the configured sequence of handlers.

9. The method of claim 1 , further comprising omitting the configured handler from the configured sequence of handlers when the handler type is the no-op handler.

10. A computing system comprising:
at least one processor; and
memory storing instructions that, when executed by the at least one processor, cause the system to:
register a handler in a configured sequence of handlers by:
receiving a configuration script defining a sequence comprising one or more handler identifiers and corresponding one or more handler arguments;
invoking a handler initialization entry point for a handler corresponding to a handler identifier of the one or more handler identifiers, the invoking the handler initialization entry point comprising:
selecting, based on the corresponding one or more handler arguments, a handler type from among two or more of:
 a configured instance of the handler;
 a configured alternate handler different from the handler;
 an alternate sequence of handlers;
 an expression; and
 a no-op handler; and
initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments; and

adding, by the processor, the configured handler to a configured sequence of handlers; and

implement a sequencer infrastructure configured to execute the configured sequence of handlers to generate an output in response to an input.

11. The computing system of claim 10 , wherein the selecting the handler type is further based on a plurality of parameters of an execution environment of the sequencer.

12. The computing system of claim 11 , wherein the parameters of the execution environment comprise:
a version number of the sequencer infrastructure;
a handler registry of handlers available to the sequencer infrastructure;
a plurality version numbers of corresponding ones of the handlers of the handler registry;
descriptions of hardware capabilities of a server comprising the processor and memory and configured to execute the sequencer; or
a location of the server.

13. The computing system of claim 11 , wherein the invoking the handler initialization entry point further comprises dynamically registering the handler with the execution environment.

14. The computing system of claim 13 , wherein the handler is retrieved from a remote source over a network.

15. The computing system of claim 10 , wherein the sequencer executing the configured sequence of handlers processes requests and generates responses in a content delivery network.

16. The computing system of claim 10 , wherein the sequencer executing the configured sequence of handlers processes requests and generates responses in a web application server.

17. The computing system of claim 10 , wherein the sequencer processes input data in a stream processing pipeline corresponding to the configured sequence of handlers.

18. The computing system of claim 10 , wherein the memory further stores instructions that, when executed by the at least one processor, cause the system to omit the configured handler from the configured sequence of handlers when the handler type is the no-op handler.

19. A method, for registering a handler in a configured sequence of handlers, the method comprising:
receiving, by a processor and memory storing instructions implementing a sequencer infrastructure, a configuration script defining a sequence comprising one or more handler identifiers and corresponding one or more handler arguments;
invoking, by the processor, a handler initialization entry point for a handler corresponding to a handler identifier of the one or more handler identifiers, the invoking the handler initialization entry point comprising:
selecting, based on the corresponding one or more handler arguments and a plurality of parameters of an execution environment of a sequencer, a handler type from among two or more of:
a configured instance of the handler;
a configured alternate handler different from the handler;
an alternate sequence of handlers;
an expression; and
a no-op handler; and

initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments;

adding, by the processor, the configured handler to a configured sequence of handlers; and
executing, by the sequencer of the sequencer infrastructure, the configured sequence of handlers to generate an output in response to an input.

20. The method of claim 19 , wherein the invoking the handler initialization entry point further comprises dynamically registering the handler with the execution environment.

Assignees

• Level 3 Communications Llc

Inventors

• Crowder William

Classifications

• G06F13/20 Primary

  for access to input/output bus · CPC title

• G06F2213/40

  Bus coupling · CPC title

• G06F9/5038 Primary

  considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups) · CPC title

• G06F9/4843

  by program, e.g. task dispatcher, supervisor, operating system · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title