Hi all, Stub objects are surrogates that support exactly the same set of remote interfaces defined by the actual implementation of a remote object. A skeleton is a server-side entity that dispatches calls to the actual remote object implementation. The dispatch logic is to unmarshals any arguments from the input stream obtained from the call object, invokes the method (indicated by the operation number opnum) on the actual remote object implementation obj, and marshals the return value or throws an exception if one occurs during the invocation. Correct me if i m wrong and any add-on information will be appreciated. Cheers.
Stubs and Skeleton were introduced with the RMI to remove the Remote Invocation Logic that were earlier made by RPC etc. It actually encapsulates the Serialization and Deserialization Logic between the client and Server talks. It provides location transparency to remote object invocation, and other network specific issues like marshalling and demarshalling of objects is done in a simpler way of serialization and deserialization of java objects and transferring the objects from one JVM to the other remote JVM. Hope it helps ............ ------------------ enJoy Life with Technology ;-)
Hi All, This does'nt contain Method Signatures. IT contain logic about packaging the arguments list , depackaging , location transparency,Marshalling .... bye
Originally posted by Leena Diwan: Hi !! Stubs and skeletons contain the method signatures of the remote objects. Anyone would like to comment ? Regards.. Leena
Manas , you will get more idea about the STUB & SKELETON in rmi / corba forum. Briefly , you can say that it is java extention of RPC ( Remote Procedure Call ) . Offcourse for distributed systems.