Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Performance Evaluation Of RMI
#1

[attachment=1699]

Performance Evaluation Of RMI

INTRODUCTION
1.Abstract
With the proliferation of the internet and network services ,there is an abundance of distributed applications such as e-commerce and other web based applications that seek to leverage the power of the internet. RMI is increasingly being used in Internet based applications as a Java only solution to the challenges facing distributed application developers. One of these challenges includes delivering better performance to end-users to satisfy their demand for better quality of service. This project addresses this need and empirically evaluates the performance of a distributed object application designed and built using RMI.
1.2 REMOTE METHOD INVOCATION
Remote method invocation (RMI) allows a Java object that executes on one machine to invoke a method of a Java object that executes on another machine. This feature aids in building distributed applications.
A remote object is one whose methods can be invoked from another Java virtual machine, potentially on a different host. An object of this type is described by one or more remote interfaces written in the Java programming language. A reference to a remote object can be passed as an argument or returned as a result in any method invocation.
1.3 EXISTING SYSTEM
Invocation of a remote object can be achieved by means of the existing methods namely: General, Activation and Custom Socket factory methods. In the General method, the server creates a number of remote objects, makes references to those remote objects accessible, and waits for clients to invoke methods on those remote objects. The client gets a remote reference to one or more remote objects in the server and then invokes methods on them. The Activation method allows objects to begin execution on an as-needed basis. This mechanism provides persistent references to objects and manages the execution of object implementations. The Socket Factory method allows customized implementation of sockets to cater to the user requirements. The amount and the type of data that can be sent over the channel can be specified.
1.4 PROPOSED SYSTEM
It is proposed to evaluate the performance of the three methods (General, Activation and Custom Socket Factory) by transferring different types of files such as text, image and video .These files are transferred using the three invocation methods and their performance is evaluated by analyzing the parameters: round trip time, latency and transmission rate. The observations are tabulated and graphs are drawn to facilitate the comparison of the three methods of remote invocation. This offers the user an insight into the best suitable method.
A Search mechanism is proposed to be implemented to locate methods when the host does not know where the method actually resides. This system is categorized into Keyword based search and Extension based search. A user friendly GUI that will hide the low level details is to be developed which will provide easier access to the three methods of invocation and will display the results of the actions performed.
Reply

#2

[attachment=6890]
Remote Method Invocation


Network Programming Paradigms


Sockets programming: design a protocol first, then implement clients and servers that support the protocol.
RMI: Develop an application, then move some objects to remote machines.
Not concerned with the details of the actual communication between processes everything is just method calls.

Call Semantics

Method Call Semantics what does it mean to make a call to a method?
How many times is the method run?
How do we know the method ran at all?
RMI does a great job of providing natural call semantics for remote objects/methods.
Simply a few additional Exceptions that you need to handle.
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

Powered By MyBB, © 2002-2024 iAndrew & Melroy van den Berg.