COMMUNICATION TECHNOLOGIES
The final technology grouping is those technologies that provide the means for the various components and services within a J2EE application to communicate with each other – a distributed application would be pretty ineffectual if these technologies didn’t provide the ‘glue’ to hold it all together.
Internet Protocols
A client request and the server’s responses are communicated over three main protocols.
HTTP
HTTP or Hypertext Transfer Protocol is a generic, stateless, application-level protocol, which has many uses beyond simply hypertext capabilities. It works on a request/response basis. A client sends a request to a server in the form of a request method, URI (Uniform Resource Identifier), and protocol version, followed a MIME-like message containing request modifiers, client information, and possible body content over a connection with a server. The server in turn responds with a ststus line followed by a MIME-like message containing server information, entity-meta information, and possible entity-body content.
TCP/IP
TCP(Transmission Control Protocol) over IP(Internet Protocol) is actually two separate protocols, which are typically combined into a single entity. IP is a protocol that takes care of making sure that data is received by both endpoints in communication over the Internet. When we type the address of the website into our browser, IP is what ensures that our request and the fulfillment of those requests make it to the proper destinations. TCP is the protocol that keeps track of the packets and make sure they are assembled in the same order as they were dispatched and are error free. Therefore, TCP and IP work together to move data around on the Internet.
SSL
Secure Sockets Layer (SSL) uses cryptography to encrypt the flow of information between the client and the server. This also provides a means for both parties to authenticate each other.
Internet Protocols
A client request and the server’s responses are communicated over three main protocols.
HTTP
HTTP or Hypertext Transfer Protocol is a generic, stateless, application-level protocol, which has many uses beyond simply hypertext capabilities. It works on a request/response basis. A client sends a request to a server in the form of a request method, URI (Uniform Resource Identifier), and protocol version, followed a MIME-like message containing request modifiers, client information, and possible body content over a connection with a server. The server in turn responds with a ststus line followed by a MIME-like message containing server information, entity-meta information, and possible entity-body content.
TCP/IP
TCP(Transmission Control Protocol) over IP(Internet Protocol) is actually two separate protocols, which are typically combined into a single entity. IP is a protocol that takes care of making sure that data is received by both endpoints in communication over the Internet. When we type the address of the website into our browser, IP is what ensures that our request and the fulfillment of those requests make it to the proper destinations. TCP is the protocol that keeps track of the packets and make sure they are assembled in the same order as they were dispatched and are error free. Therefore, TCP and IP work together to move data around on the Internet.
SSL
Secure Sockets Layer (SSL) uses cryptography to encrypt the flow of information between the client and the server. This also provides a means for both parties to authenticate each other.
Secure HTTP (HTTPs) is usually distinguished from regular unencrypted HTTP by being served on a different port number.
Remote object Protocols
In applications where the components are often distributed across many tiers and servers, some mechanism for using the components remotely I srequired, preferably leaving the client unaware that the component is not local to itself.
RMI and RMI-IIOP
Remote Method Invocation (RMI) is one of the primary mechanism in distributed object applications. It allows us to use interface to define remote objects. We can then call methods on these remote objects as if
they were local. The exact wire-level transportation mechanism is implementation-specific.
RMI-IIOP is an extension of RMI but over IIOP (Inter-ORB Protocol) , which allows us to define a remote interface to any remote object that can be implemented in any language that supports OMG mapping and ORB.
Remote object Protocols
In applications where the components are often distributed across many tiers and servers, some mechanism for using the components remotely I srequired, preferably leaving the client unaware that the component is not local to itself.
RMI and RMI-IIOP
Remote Method Invocation (RMI) is one of the primary mechanism in distributed object applications. It allows us to use interface to define remote objects. We can then call methods on these remote objects as if
they were local. The exact wire-level transportation mechanism is implementation-specific.
RMI-IIOP is an extension of RMI but over IIOP (Inter-ORB Protocol) , which allows us to define a remote interface to any remote object that can be implemented in any language that supports OMG mapping and ORB.
No comments:
Post a Comment