RPC vs RMI
Posted 2006. 8. 29. 00:36RMI is focused on Java, with connectivity to existing systems using native methods. This means RMI can take a natural, direct, and fully powered approach to provide a distributed computing technology that allows us to add Java functionality throughout the system. To get the cross-platform portability that Java provides, RPC requires a lot more overheads than RMI. RPC has to convert the arguments between architecture so that each computer can use its native datatype. RMI’s biggest limitation is it can only call methods in Java. To call methods written in other languages it has to rely on other technologies like JNI, JDBC, RMI-IIOP, RMI-IDL etc. Whereas RPC does not translate well into Distributed object systems, where program-level objects residing in different address space is needed.
invalid-file이전에 공부하던 자료인데 쓰려면 다 쓸데가 있나보다.
미들웨어의 기초적 설명
- Filed under : S/W Architecture
