Virtual mode execution manager
US-12118376-B2 · Oct 15, 2024 · US
US10540201B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10540201-B2 |
| Application number | US-201715664207-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 31, 2017 |
| Priority date | Jul 31, 2017 |
| Publication date | Jan 21, 2020 |
| Grant date | Jan 21, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods and apparatus for task processing in a distributed environment are disclosed and described. An example apparatus includes a task manager and a task dispatcher. The example task manager is to receive a task and create an execution context for the task, the execution context to associate the task with a routine for task execution. The example task dispatcher is to receive a report of task execution progress and provide an update regarding task execution progress, the task dispatcher, upon initiation of task execution, to facilitate blocking of interaction with a resource involved in the task execution. The example task dispatcher is to trigger an indication of task execution progress and, upon task finish, facilitate unblocking of the resource involved in the task execution.
Opening claim text (preview).
What is claimed is: 1. An apparatus comprising: memory; and at least one processor to implement: a task manager in a virtual machine to receive a task and create an execution context for the task, the execution context to associate the task with a routine for task execution; and a task dispatcher in the virtual machine to receive a report of task execution progress and provide an update regarding task execution progress, the task dispatcher, upon initiation of task execution, to facilitate blocking of interaction with a resource involved in the task execution, the task dispatcher to trigger an indication of task execution progress and, upon task finish, facilitate unblocking of the resource involved in the task execution. 2. The apparatus of claim 1 , wherein the resource includes a graphical user interface. 3. The apparatus of claim 2 , where the indication includes a graphical display identifying the task and providing a visible indicator of task progress. 4. The apparatus of claim 3 , wherein the graphical display is to be updated based on an update from the task dispatcher regarding task execution progress. 5. The apparatus of claim 1 , wherein the task manager is to be triggered by a server to create the execution context in response to receiving the task for execution from a client. 6. The apparatus of claim 5 , wherein the server includes a task endpoint to receive the task. 7. The apparatus of claim 5 , wherein the server is to communicate with the client via a data communication layer. 8. A non-transitory computer readable storage medium comprising instructions that, when executed, cause a machine to at least: create, in a virtual machine, an execution context for a received task, the execution context to associate the task with a routine for task execution; upon initiation of task execution, facilitate blocking of interaction with a resource involved in the task execution; receive a report of task execution progress and trigger display of an indication of task execution progress; and upon task finish, facilitate unblocking of the resource involved in the task execution. 9. The storage medium of claim 8 , wherein the resource includes a graphical user interface. 10. The storage medium of claim 9 , where the indication includes a graphical display identifying the task and providing a visible indicator of task progress. 11. The storage medium of claim 10 , where in the instructions, when executed, further cause the machine to update the graphical display based on an update from a task dispatcher regarding task execution progress. 12. The storage medium of claim 8 , wherein the instructions, when executed, further cause the machine to trigger a task manager to create the execution context in response to receiving the task for execution from a client. 13. The storage medium of claim 12 , wherein the machine communicates with the client via a data communication layer. 14. A method comprising: creating, in a virtual machine using at least one processor, an execution context for a task, the execution context to associate the task with a routine for task execution; upon initiation of task execution, facilitating, using the at least one processor, blocking of interaction with a resource involved in the task execution; receiving, using the at least one processor, a report of task execution progress and trigger display of an indication of task execution progress; and upon task finish, facilitating, using the at least one processor, unblocking of the resource involved in the task execution. 15. The method of claim 14 , wherein the resource includes a graphical user interface. 16. The method of claim 15 , where the indication includes a graphical display identifying the task and providing a visible indicator of task progress. 17. The method of claim 16 , further including updating the graphical display based on an update regarding task execution progress. 18. The method of claim 14 , wherein creating the execution context is triggered in response to receiving the task at a server for execution from a client. 19. The method of claim 18 , wherein the server includes a task endpoint to receive the task. 20. The method of claim 18 , wherein the server is to communicate with the client via a data communication layer.
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
Hypervisor-specific management and integration aspects · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
in the data link layer [OSI layer 2], e.g. HDLC · CPC title
Instruction set architectures of guest OS and hypervisor or native processor differ, e.g. Bochs or VirtualPC on PowerPC MacOS · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.