Dcom, Corba, Java Rmi: Konsep Dan Teknik Dasar Pemrograman

DCOM, CORBA, dan Java RMI adalah middleware yang memungkinkan komputasi jarak jauh atau komputasi tersebar. Meskipun telah terdapat konsep layanan web dan implementasi yang diterapkan dalam berbagai kasus saat ini, ketiga middleware di atas masih sering digunakan untuk lingkungan yang application-specific, yang membutuhkan performa lebih baik. Paper ini diharapkan akan memberikan gambaran mengenai DCOM, CORBA, dan Java RMI dari konsep hingga perbedaan yang paling mendasar terkait teknik pemrograman. DCOM, CORBA, and Java RMI are middleware that enable remote computing (distributed computing). Although we have Web Service concept and implementation that applied in many cases right now, all three still often used for applications-specific nature, which need the better performance. This paper is intended to give an overview of DCOM, CORBA, and Java RMI, from concept to most fundamental differences related to programming techniques

DCOM, CORBA, JAVA RMI: KONSEP DAN TEKNIK DASAR PEMROGRAMAN

DCOM, CORBA, dan Java RMI adalah middleware yang memungkinkan komputasi jarak jauh atau komputasi tersebar. Meskipun telah terdapat konsep layanan web dan implementasi yang diterapkan dalam berbagai kasus saat ini, ketiga middleware di atas masih sering digunakan untuk lingkungan yang application-specific, yang membutuhkan performa lebih baik. Paper ini diharapkan akan memberikan gambaran mengenai DCOM, CORBA, dan Java RMI dari konsep hingga perbedaan yang paling mendasar terkait teknik pemrograman. DCOM, CORBA, and Java RMI are middleware that enable remote computing (distributed computing). Although we have Web Service concept and implementation that applied in many cases right now, all three still often used for applications-specific nature, which need the better performance. This paper is intended to give an overview of DCOM, CORBA, and Java RMI, from concept to most fundamental differences related to programming techniques

Utilizing Object Compression for Better J2ME Remote Method Invocation in 2.5G Networks

This paper introduces two new Java 2 Platform Micro Edition (J2ME) Remote Method Invocation (RMI) packages. These packages make use of serialized object compression and encryption in order to respectively minimize the transmission time and to establish secure channels. The currently used J2ME RMI package does not provide either of these features. Our packages substantially outperform the existing Java package in the total time needed to compress, transmit, and decompress the object for General Packet Radio Service (GPRS) networks, often called 2.5G networks, even under adverse conditions. The results show that the extra time incurred to compress and decompress serialized objects is small compared to the time required to transmit the object without compression in GPRS networks. Existing RMI code for J2ME can be obliviously used with our new packages

Java Grande Forum Report: Making Java Work for High-End Computing

This document describes the Java Grande Forum and includes its initial deliverables.Theseare reports that convey a succinct set of recommendations from this forum to SunMicrosystems and other purveyors of Java™ technology that will enable GrandeApplications to be developed with the Java programming language

Vers une programmation locale et distribuée unifiée au travers de l'utilisation de conteneurs actifs et de références asynchrones.

Dans le domaine des systèmes distribués, la notion de mobilité du code est à l’origine de nombreux travaux visant à améliorer les performances des applications parallèles (processus légers mobiles), à faciliter le développement d’applications (agents mobiles) ou à garantir la sécurité (cartes à puces). Dans ce contexte, nous montrons que les systèmes d’agents mobiles ont peu à peu disparu au profit de plates-formes d’exécution asynchrones. Nous présentons une nouvelle abstraction – appellée conteneur actif – qui est issue d’une modélisation en π-calcul d’un système d’agents mobiles, et qui semble être une brique de base avec laquelle les applications distribuées peuvent être conçues. Le développement d’une implémentation de cette abstraction en Java a fait apparaître un problème lié à la gestion de la concurrence dans les applications, distribuées ou non. Nous décrivons donc la notion de référence asynchrone – notre solution à ce problème – qui permet d’exprimer simplement la concurrence d’exécution dans une application. Notre implémentation en Java de ce concept facilite le développement des applications multithread ées et parallèles, en évitant le recours problématique aux threads par l’utilisation exclusive d’un unique paradigme : l’appel de méthode. Ce dernier peut se décliner en de multiples versions : synchrone, asynchrone, local ou distant. L’ensemble de nos travaux est disponible sous licence libre LGPL au sein d’une plateforme opérationnelle et documentée appellée Mandala qui est brièvement décrite.In the domain of distributed systems, several projects focus on mobile code in order to enhance the performance of parallel applications (mobile threads), to make easier the development of applications (mobile agents) or to guarantee security (smart cards). In this context, we show how mobile agent systems have basically disappeared in favor of asynchronous execution frameworks. We present a new abstraction – called active container – originating from a model of a mobile agents system. It seems to be a base layer on top of which distributed applications can be developped. A Java implementation of this abstraction raises a problem related to the management of concurrency in applications, distributed or not. We describe the notion of asynchronous reference – our solution to this problem – which allows to express concurrency quite easily. Our Java implementation of this concept eases the development of multithreaded and parallel applications avoiding the problematic use of threads by the exclusive use of a single paradigm: method invocation. This can be: synchronous, asynchronous, local or remote. Our work is available as an open-source LGPL licence package within a ready to use and documented framework called Mandala which is briefly described

Proceedings of the 4th International Conference on Principles and Practices of Programming in Java

This book contains the proceedings of the 4th international conference on principles and practices of programming in Java. The conference focuses on the different aspects of the Java programming language and its applications

Reflective Remote Method Invocation

Remote Method Invocation (RMI) is available in the current Java language design and implementation, providing the much-needed capability of allowing objects running in different Java processes to collaborate using a variation on the popular Remote Procedure Call (RPC). Although RMI provides features which are desirable for high-performance distributed computing, its design and implementation are deficient in key areas of importance to the high-performance computing community in general. This paper addresses the key deficiencies of RMI and how these deficiencies affect the design and implementation of distributed object applications. Reflective RMI (RRMI) is an open RMI implementation which makes better use of the object-oriented features of Java. RRMI is so-called reflective because it directly employs the reflection capabilities of the current Java language to invoke methods remotely. RRMI makes use of the dynamic class loader (a class called NetClassLoader) to allow client/server app..

Reflective Remote Method Invocation

Remote Method Invocation (RMI) is available in the current Java language design and implementation, providing the much-needed capability of allowing objects running in different Java processes to collaborate using a variation on the popular Remote Procedure Call (RPC). Although RMI provides features which are desirable for high-performance distributed computing, its design and implementation are deficient in key areas of importance to the high-performance computing community in general. This paper addresses the key deficiencies of RMI and how these deficiencies affect the design and implementation of distributed object applications. Reflective RMI (RRMI) is an open RMI implementation which makes better use of the object-oriented features of Java. RRMI is so-called reflective because it directly employs the reflection capabilities of the current Java language to invoke methods remotely. RRMI makes use of the dynamic class loader (a class called NetClassLoader) to allow client/server applications to be built for high-performance computing system