Transparency and asynchronous method invocation

Authors:
Pierre Vignéras
Affiliations:
GIK Institute of Engineering Sciences and Technology, Topi, N.W.F.P, Pakistan
Venue:
OTM'05 Proceedings of the 2005 Confederated international conference on On the Move to Meaningful Internet Systems - Volume >Part I
Year:
2005

Citing 9
Cited 0

Concurrent programming using actors: exploiting large-scale parallelism

Distributed Artificial Intelligence
Systematic concurrent object-oriented programming

Communications of the ACM
Toward a method of object-oriented concurrent programming

Communications of the ACM
Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
Active object: an object behavioral pattern for concurrent programming

Pattern languages of program design 2
A more efficient RMI for Java

JAVA '99 Proceedings of the ACM 1999 conference on Java Grande
Concurrent Programming in Java. Second Edition: Design Principles and Patterns

Concurrent Programming in Java. Second Edition: Design Principles and Patterns
RMIX: A Multiprotocol RMI Framework for Java

IPDPS '03 Proceedings of the 17th International Symposium on Parallel and Distributed Processing
Actors: a model of concurrent computation in distributed systems (parallel processing, semantics, open, programming languages, artificial intelligence)

Actors: a model of concurrent computation in distributed systems (parallel processing, semantics, open, programming languages, artificial intelligence)

Quantified Score

Hi-index	0.00

Visualization

Abstract

This article focuses on transparency in the context of asynchronous method invocation. It describes two solutions available to provide full-transparency: where asynchronism is entirely masked to the developer. The main contribution of this paper is to clearly present the drawbacks of this approach: exception handling and developer consciousness are two problems inherent to full-transparency that makes it at least, hard to use, at worst, useless. This paper defends explicit asynchronous method invocation and proposes semi-transparency: almost all the complexity of asynchronism is masked to the developer but the asynchronism itself.