Supposedly I want to
create a client-server communication model like the following figure.
We use the word "tier" in software development. what
does "tier" mean? Tier, (pronunciation: Tee ya), is a layer.
Here, you may rise the question - "why do you want to
create application client?". Let's say, I am a backend programmer who
usually write programs to solve complicated business workflows.
The problem is how we do testing effectively the programs
what we write, before users use it. We don't want to wait for the frontend
programmers who normally design web pages of web tier. It is not productive.
If I can access and test without web tier, I don't need to
wait for frontend programmers' work done. we need to create a communication
between client and server without any web page. Which protocol does it need to
establish that kind of communication? It is RMI-IIOP.
RMI-IIOP (Remote Method Invocation Internet Inter-Orb Protocol) which comes out from CORBA (Common Object Request Broker Architecture) distributed computing capabilities to the Java Platform.
In Java Platform, we call components of business tier, as
EJB (Enterprise Beans). They are powerful in EJB 3.0 and later. RMI-IIOP is a
bridge to connect Application Client and EJB. RMI-IIOP is developed by Sun Micro and IBM. What are advantages?
Previously java developers created RMI (Remote Method
Invocation). RMI has some limitations. RMI's native protocol, JRMP (Java Remote
Method Protocol), can't connect with different other protocols.
It's the main story RMI-IIOP born. RMI-IIOP supports both JRMP and IIOP.
To switch from JRMP to IIOP, or vice versa, it needs only to
change some parameters in java coding. It is the transparency of RMI-IIOP. And
also, it supports to maintain java memo 'Write once, Run anywhere anytime
forever'.
Reference
No comments:
Post a Comment