I am currently learning Java RMI (Remote Method Invocation), and I followed the tutorial provided by Oracle on it´s website. I have a particular question however:
What is the use of the stub-skeleton generated by rmic? Do I really need it?
I am currently learning Java RMI (Remote Method Invocation), and I followed the tutorial provided by Oracle on it´s website. I have a particular question however:
What is the use of the stub-skeleton generated by rmic? Do I really need it?
The Stub/Skeleton hides the communication details away from the developer. The Stub is the class that implements the remote interface. It serves as a client-side placeholder for the remote object. The stub communicates with the server-side skeleton. The skeleton is the stub's counterpart on server-side. Both communicate via the network. The skeleton actually knows the real remote objects delegates the stub's request to it and returns the response to the stub. You require both as they are the essential building blocks for RMI.
UnicastRemoteObject
. –
Soredium UnicastRemoteObject
. After all some object will be created on the client machine to represent the remote object; that object is a proxy and I think can be called a stub. It certainly fills the role that the instances of the old stub classes filled. –
Manifold © 2022 - 2024 — McMap. All rights reserved.
rmi
on stack-overflow. They are the best ones seriously as compared to other official tutorials. Do you have any personal blogs related to rmi.Please,I need them! THANKS... – Apis