Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

Remote method invocation as a first-class citizen

Remote method invocation as a first-class citizen The classical remote method invocation (RMI) mechanism adopted by several object-based middleware is ‘black-box’ in nature, and the RMI functionality, i.e., the RMI interaction policy and its configuration, is hard-coded into the application. This RMI nature hinders software development and reuse, forcing the programmer to focus on communication details often marginal to the application being developed. Extending the RMI behavior with extra functionality is also a very difficult job, because added code must be scattered among the entities involved in communications. http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png Distributed Computing Springer Journals

Remote method invocation as a first-class citizen

Distributed Computing , Volume 16 (4) – Jan 1, 2003

Loading next page...
 
/lp/springer-journals/remote-method-invocation-as-a-first-class-citizen-nGRmRAIp5g

References (34)

Publisher
Springer Journals
Copyright
Copyright © 2003 by Springer-Verlag Berlin/Heidelberg
Subject
ComputerScience
ISSN
0178-2770
eISSN
1432-0452
DOI
10.1007/s00446-003-0094-8
Publisher site
See Article on Publisher Site

Abstract

The classical remote method invocation (RMI) mechanism adopted by several object-based middleware is ‘black-box’ in nature, and the RMI functionality, i.e., the RMI interaction policy and its configuration, is hard-coded into the application. This RMI nature hinders software development and reuse, forcing the programmer to focus on communication details often marginal to the application being developed. Extending the RMI behavior with extra functionality is also a very difficult job, because added code must be scattered among the entities involved in communications.

Journal

Distributed ComputingSpringer Journals

Published: Jan 1, 2003

There are no references for this article.