Didn't get: Found it difficult to understand the RPC managers..
One minute response: You and everybody else; how to best manage RPC systems is still an open question.
Didn't get: Can you be bit detail how mapping between client and server calls is done. How client maps server functions..
One minute response: At heart, it's just another name-address mapping; how much more complicated you want to get depends on the RPC system.
Didn't get: Generation of stubs of client and server; getting them. Hope project will help me out to get them..
One minute response: That's why I assign them.
Didn't get: Still not clear about the implementation.
One minute response: The thing to do is implement two or three simple RPC systems completely by hand; after the third or fourth such system you should have a good idea of what is boilerplate and can be cranked out automatically by programs..
Didn't get: RPC service availability.
One minute response: Determining if an RPC service is offered is difficult; it's one of the reasons CORBA's so complicated. Sun RPC, written mostly for LANs, fudges the issue by relying on the portmapper and well-known ports..
Didn't get: CORBA concepts are somewhat confusing (CORBA objects).
One minute response: CORBA concepts are complicated, partially because they completely embrace the object-oriented paradigm.
Didn't get: CORBA.
One minute response: It is not too far off the mark to think of CORBA as an operating system that works between a set hosts (or in the network) rather than on a single host.
Didn't get: The difference between Sun RPC and CORBA is complicated..
One minute response: In detal, but in concept the difference is simple: CORBA is like Sun RPC with a whole bunch of stuff heaped on top. The difference between the RPC part of CORBA and Sun RPC is also complicated, but CORBA works hard to keep the RPC mechanism hidden.
This page last modified on 25 March 2003.