1, B / S structure, from server-side S is unable to actively "push" operation, but RMI can,
After the client lookup to a server-side remote object, you can register a remote object existing on the client side, so that the server side can actively "push" information to the client, the most typical is from the server side update Certain states of the client interface, this is the server side. I guess JMS is probably made according to this principle.
2, RMIC has 2 parameters - V1.1 and -V1.2.
If the parameters are parameters - V1.1, Stub and Skel are generated;
If the parameter-V1.2 generates only STUB. You can use it, don't worry.
3, Server_
Stub.class is a copy of the RMI service on the local machine called the stub,
The client is connected to the server with the server, so you need to install all the .class files below the Client to the client. SERVER_
Skel.class is responsible for waiting for the server side, called a frame,
It connects the server to server_stub.class to install it with all the .class files below the Server to the server. JDK1.2 The above version has built-in framework, and does not need to be generated, but we need to compatibility with low version of JDK.
4, Q: Where is the remote method in RMI and CORBA?
A:
For RMI, the remote method of the Client end is executed by the settle program; the remote method of the Server end is performed by the frame program.
