Techniques for hybrid computer thread creation and management
US-2016239338-A1 · Aug 18, 2016 · US
US10241825B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10241825-B2 |
| Application number | US-201715689580-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 29, 2017 |
| Priority date | Jul 13, 2012 |
| Publication date | Mar 26, 2019 |
| Grant date | Mar 26, 2019 |
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.
A technique for operating a computer system to support an application, a first application server environment, and a second application server environment includes intercepting a work request relating to the application issued to the first application server environment prior to execution of the work request. A thread adapted for execution in the first application server environment is created. A context is attached to the thread that non-disruptively modifies the thread into a hybrid thread that is additionally suitable for execution in the second application server environment. The hybrid thread is returned to the first application server environment.
Opening claim text (preview).
What is claimed is: 1. A computer system configured to support an application, a first application server environment, and a second application server environment, the system comprising: a memory and a processor, wherein the processor is configured to execute instructions for each of the components stored in the memory; a request interceptor component configured to intercept a work request relating to the application issued to the first application server environment prior to execution of the work request; an executor component configured to, responsive to the request interceptor component, create a thread adapted for execution in the first application server environment; a thread dispatcher component configured to, responsive to the executor component, attach a context to the thread to non-disruptively modify the thread into a hybrid thread that is additionally suitable for execution in the second application server environment; wherein the context comprises transactional control data of one of the application server environments, security control data of one of the application server environments, monitoring control data of one of the application server environments, diagnostic tracing control data of one of the application server environments, and data enabling access to an application programming interface of one of the application server environments; wherein the hybrid thread is operable to execute in the first application server environment and in the second application server environment without requiring modification of the first and second application server environment; wherein the hybrid thread comprises first data that is only visible to a server in the first application server environment and second data is only visible to another server in the second application server environment; wherein the first application server environment and the second application server environment are incompatible in their program execution models; and wherein only one of the first application server environment and the second application server environment is a procedural program environment; and a catcher component configured to, responsive to the thread dispatcher component, return the hybrid thread to the first application server environment.
Instruction issuing, e.g. dynamic instruction scheduling or out of order instruction execution · CPC title
Multiprogramming arrangements · CPC title
considering hardware capabilities · CPC title
by program, e.g. task dispatcher, supervisor, operating system · CPC title
by interrupt, e.g. masked · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.