Creating endpoints

Patent metadata

Field	Value
Publication number	US-11121970-B2
Application number	US-202015929704-A
Country	US
Kind code	B2
Filing date	May 18, 2020
Priority date	Jul 24, 2018
Publication date	Sep 14, 2021
Grant date	Sep 14, 2021

Abstract

A device receives a configuration file that includes an object concerning a Hypertext Transfer Protocol (HTTP) route. The object includes a parameter, related to the HTTP route, that includes one or more elements related to the HTTP route, and includes an attribute related to an HTTP action. The device parses the configuration file to recognize the object, and parses the object to recognize the parameter. The device creates the HTTP route based on the parameter. The HTTP route includes information concerning the one or more elements related to the HTTP route and the attribute related to the HTTP action, and sends the HTTP route to a server, causing the server to perform an operation based on the HTTP route.

First claim

What is claimed is:

1. A method, comprising:
receiving, by a device, a configuration file,
wherein the configuration file includes data concerning a Hypertext Transfer Protocol (HTTP) route;

parsing, by the device, the data concerning the HTTP route to determine:
a parameter related to the HTTP route, and
an attribute related to an HTTP action; and

creating, by the device, the HTTP route and an HTTP verb declaration based on the parsing of the data concerning the HTTP route.

2. The method of claim 1 , wherein the HTTP route includes computer code, conforming to a domain specific language, that causes creation of an endpoint by a server device.

3. The method of claim 1 , wherein the configuration file further includes data concerning at least one other HTTP route; and
wherein the method further comprises:
creating the at least one other HTTP route based on the data concerning the at least one other HTTP route.

4. The method of claim 1 , further comprising:
determining that the configuration file uses a particular format; and
wherein parsing the data concerning the HTTP route comprises:
parsing the data concerning the HTTP route based on the particular format.

5. The method of claim 1 , wherein creating the HTTP route comprises:
including, in the HTTP route, information concerning the parameter and the attribute.

6. The method of claim 1 , further comprising:
adding, to the HTTP route, computer code that defines an exception handler or exception handling routine.

7. The method of claim 1 , wherein the parameter includes one or more elements of an HTTP path associated with an application programming interface resource associated with the HTTP route.

8. A device, comprising:
one or more memories; and
one or more processors coupled to the one or more memories, configured to:
receive a configuration file,
wherein the configuration file includes data concerning a Hypertext Transfer Protocol (HTTP) route;

parse the data concerning the HTTP route to determine:
a parameter related to the HTTP route, and
an attribute related to an HTTP action; and

create the HTTP route and an HTTP verb declaration based on the parsing of the data concerning the HTTP route.

9. The device of claim 8 , wherein the HTTP route includes computer code, conforming to a domain specific language, that causes creation of an endpoint by a server device.

10. The device of claim 8 , wherein the configuration file further includes data concerning at least one other HTTP route; and
wherein the one or more processors are further configured to:
create the at least one other HTTP route based on the data concerning the at least one other HTTP route.

11. The device of claim 8 , wherein the one or more processors are further configured to:
determine that the configuration file uses a particular format; and
wherein the one or more processors, when parsing the data concerning the HTTP route, are further configured to:
parse the data concerning the HTTP route based on the particular format.

12. The device of claim 8 , wherein the one or more processors, when creating the HTTP route, are further configured to:
include, in the HTTP route, information concerning the parameter and the attribute.

13. The device of claim 8 , wherein the one or more processors are further configured to:
add, to the HTTP route, computer code that defines an exception handler or exception handling routine.

14. The device of claim 8 , wherein the parameter includes one or more elements of an HTTP path associated with an application programming interface resource associated with the HTTP route.

15. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
receive a configuration file,
wherein the configuration file includes data concerning a Hypertext Transfer Protocol (HTTP) route;

parse the data concerning the HTTP route to determine:
a parameter related to the HTTP route, and
an attribute related to an HTTP action; and

create the HTTP route and an HTTP verb declaration based on the parsing of the data concerning the HTTP route.

16. The non-transitory computer-readable medium of claim 15 , wherein the HTTP route includes computer code, conforming to a domain specific language, that causes creation of an endpoint by a server device.

17. The non-transitory computer-readable medium of claim 15 , wherein the configuration file further includes data concerning at least one other HTTP route; and
wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
create the at least one other HTTP route based on the data concerning the at least one other HTTP route.

18. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
determine that the configuration file uses a particular format; and
wherein the one or more instructions, that cause the one or more processors to parse the data concerning the HTTP route, cause the one or more processors to:
parse the data concerning the HTTP route based on the particular format.

19. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the one or more processors to create the HTTP route, cause the one or more processors to:
include, in the HTTP route, information concerning the parameter and the attribute.

20. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
add, to the HTTP route, computer code that defines an exception handler or exception handling routine.

Assignees

• Capital One Services Llc

Inventors

• Gupte Saurabh

Classifications

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• G06F9/44505

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• H04W4/70

  Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L45/72 Primary

  Routing based on the source address · CPC title