> I am new to rmi but am curious as to why do u use
> UnicastRemoteObject and why not RemoteObject or
> RemoteServer.
If you look at the java API RempteObject is the superclass of RemoteServer and RemoteServer is in turn the superclass of UnicastRemoteObject. RemoteObject provides basic remote object semantics for servers and stubs. RemoteServer provides getClientHost an dgetLog methods while UnicastRemoteObject supports simple transient point to point RMI servers.
> Plus can anybody tell me some of the
> semantics of UnicastRemoteObject.
A unicasr remote object has the following characteristics.
references/remote stubs are valid only for at most the life cycle of teh the proces that creates the remote object.
communication with reote object uses TCP transport.
invocations, parameters and results use a stream protocol for communicating between client and server.
Unicast indicates point to point communications. A unicast remote object is a TCP/IP server which listens at a TCP/IP port.