US 12,003,574 B1
Processing distributed jobs using multiple connections
Denis Gladkikh, Redmond, WA (US); and Mitchell Blank, Jr., San Francisco, CA (US)
Assigned to Splunk Inc., San Francisco, CA (US)
Filed by Splunk Inc., San Francisco, CA (US)
Filed on Jan. 7, 2022, as Appl. No. 17/571,058.
Application 17/571,058 is a continuation of application No. 16/922,632, filed on Jul. 7, 2020, granted, now 11,252,224.
Application 16/922,632 is a continuation of application No. 16/296,685, filed on Mar. 8, 2019, granted, now 10,713,245, issued on Jul. 14, 2020.
Application 16/296,685 is a continuation of application No. 15/965,278, filed on Apr. 27, 2018, granted, now 10,255,322, issued on Apr. 9, 2019.
Application 15/965,278 is a continuation of application No. 14/813,908, filed on Jul. 30, 2015, granted, now 9,983,912, issued on May 29, 2018.
Application 14/813,908 is a continuation of application No. 14/448,048, filed on Jul. 31, 2014, granted, now 9,128,779, issued on Sep. 8, 2015.
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 67/10 (2022.01); G06F 9/48 (2006.01); G06F 9/50 (2006.01); G06F 9/52 (2006.01); G06F 9/54 (2006.01); G06F 16/245 (2019.01); G06F 16/2453 (2019.01); G06F 16/27 (2019.01); H04L 41/0896 (2022.01); H04L 65/65 (2022.01); H04L 67/02 (2022.01)
CPC H04L 67/10 (2013.01) [G06F 9/4806 (2013.01); G06F 9/4856 (2013.01); G06F 9/5005 (2013.01); G06F 9/5011 (2013.01); G06F 9/5038 (2013.01); G06F 9/5088 (2013.01); G06F 9/52 (2013.01); G06F 9/54 (2013.01); G06F 16/245 (2019.01); G06F 16/2453 (2019.01); G06F 16/27 (2019.01); G06F 16/273 (2019.01); H04L 41/0896 (2013.01); H04L 65/65 (2022.05); H04L 67/02 (2013.01)] 16 Claims
OG exemplary drawing
 
1. A method comprising:
transmitting, by a first component of a first execution environment via a first connection to a second component of a second execution environment, a first request associated with a job;
receiving, by the first component via a second connection from the second component, a pull synchronization request;
transmitting, by the first component via the second connection to the second component, a response to the pull synchronization request, the response comprising data associated with the job;
receiving, in response to the first request, by the first component via the first connection from the second component, a result of the job, wherein the result is based on the response to the pull synchronization request; and
responsive to receiving the result, closing the first connection and keeping the second connection open.