Domain name service based remote programming objects
US-9313167-B1 · Apr 12, 2016 · US
US9513980B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9513980-B2 |
| Application number | US-90764510-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 19, 2010 |
| Priority date | Oct 19, 2010 |
| Publication date | Dec 6, 2016 |
| Grant date | Dec 6, 2016 |
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.
Systems and methods consistent with the invention may include using asynchronous communication and scopes to transparently decouple modules and distribute load. Asynchronous communication may be achieved by using message queues or by using message topics. Scopes are introduced as a means to provide structure to resources associated with the decoupled modules and to improve the ability to distribute such resources necessary to process messages between modules. Furthermore, the use of asynchronous communication and scopes may be done automatically and transparently to the user and/or application developers.
Opening claim text (preview).
What is claimed is: 1. A method for decoupling modules in a computer system, comprising: sending a message, by a first module in a first host, to a second module in a second host by means of asynchronous messaging; maintaining, in scopes managed in a scope hierarchy, a context containing one or more resources needed to process the message; sending, to the second host, a copy of the context; pausing the first module; receiving a response indicating that the message has been processed by the second module; receiving, from the second host, updates to the copy of the context; incorporating the updates into the context in the scope hierarchy; and resuming the first module on the first host. 2. The method of claim 1 wherein the sending of the message and the sending the copy of the context are transparent to the first module and the second module. 3. The method of claim 1 , wherein receiving the response includes receiving a reply message at the first host from the second host. 4. The method of claim 1 , wherein the copy of the context is attached to the message as an in-band copy. 5. The method of claim 1 , further comprising sending the copy of the context to the second host separate from the message as an out-of-band copy. 6. The method of claim 5 , wherein sending the context to the second host comprises proactively copying the context on behalf of the first host. 7. The method of claim 5 , wherein sending the copy of the context comprises copying the context on demand of the second host. 8. The method of claim 1 , wherein the context needed to process the message is identifiable in the hierarchy of scopes. 9. The method of claim 1 , further comprising placing the message in a message queue. 10. The method of claim 9 further comprising: pausing the queue, updating the second module, and processing the request message from the queue after the second module is updated. 11. The method of claim 9 , further comprising: providing a series of second hosts configured to process the message based on the copy of the context; and using a load-balancer to route the message to more than one of these hosts. 12. A non-transitory computer-readable medium storing instructions for executing a method for decoupling modules in a computer system, the method comprising: sending a message, by a first module in a first host, to a second module in a second host by means of asynchronous messaging; maintaining, in scopes managed in a scope hierarchy, a context containing one or more resources needed to process the message; sending, to the second host, a copy of the context; pausing the first module; receiving a response indicating that the message has been processed by the second module: receiving, from the second host, updates to the copy of the context; incorporating the updates into the context in the scope hierarchy; resuming the first module on the first host.
Object oriented; Remote method invocation [RMI] (non-remote method invocation G06F9/449) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.