| Encapsulating concurrency with Early-Reply |
| Full text |
Pdf
(233 KB)
|
| Source
|
Conference on Object Oriented Programming Systems Languages and Applications
archive
Companion of the 17th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
table of contents
Seattle, Washington
SESSION: Doctoral symposium
table of contents
Pages: 18 - 19
Year of Publication: 2002
ISBN:1-58113-626-9
|
|
Author
|
|
| Sponsor |
|
| Publisher |
|
| Bibliometrics |
Downloads (6 Weeks): 0, Downloads (12 Months): 13, Citation Count: 0
|
|
|
ABSTRACT
Component methods often produce their final parameter values long before the method body is ready to terminate. To minimize client blocking, Early-Reply can be used to forward invocation results to the caller as soon as they are (safely) available. After executing Early-Reply, the method remainder and the client caller can proceed concurrently, modulo synchronization constraints. The prime motivation for Early-Reply, then, is to improve performance factors such as response time and resource utilization.Early-Reply received previous attention as a construct for explicit concurrent programming. It's value for sequential programming, however, has not been widely recognized. The present research supplies a formal treatment of Early-Reply as a basis for concurrent execution of sequential programs. In particular, we reformulate Early-Reply under local proof obligations that encapsulate concurrency as a (temporal) unit of information hiding. The upshot is that software developers can use Early-Reply to exploit the performance benefits of concurrent execution, without compromising the reasoning benefits of sequential programming.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
|
| |
2
|
|
 |
3
|
|
| |
4
|
|
| |
5
|
|
| |
6
|
|
| |
7
|
|
| |
8
|
Michael Philippsen. A survey of concurrent object-oriented languages. Concurrency: Practice and Experience, 12(10):917--980, 2000.
|
| |
9
|
|
| |
10
|
|
| |
11
|
|
|