1, b/s structure, from server-side s is not active to the client C "push" operation, but RMI can, client lookup to a server-side remote object, you can register a remote object on the server side, so that the server can proactively to the client "push" information , the most typical of which is to update some states of the client interface from the server side, note that this is the server-side initiative. I guess JMS is probably based on this principle.
2, Rmic has 2 parameters-v1.1 and-v1.2.
Stub and Skel are generated if-v1.1 with parameters;
If a stub is generated with a parameter-v1.2 only. Can be used, don't worry.
3. The Server_ stub.class is a copy of the RMI service on the local machine, called a
stub , through which the client establishes a connection to the server, so it needs to be installed with all the. class files under Client. The Server_ skel.class is responsible for waiting for the connection on the server side, called the
framework , which will connect to the Server_stub.class on behalf of the server, and install it to the server side with all the. class files below the server. jdk1.2 the above version has a built-in framework and does not need to generate itself, but we need to be compatible with a lower version of the JDK.
4, where the remote methods in Q:rmi and CORBA are executed.
A: For RMI, the client-side remote method is executed by the stub program, and the remote method on the server side is executed by the framework program.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
