Application - Layer Protocols

Application - Application - Layer Protocols

Good morning. Yesterday, I learned about Application - Application - Layer Protocols. Which may be very helpful to me and you. Application - Layer Protocols

We have just learned that network processes communicate with each other by sending messages into sockets. But how are these messages structured? What are the meanings of the assorted fields in the messages? When do the processes send the messages? These questions bring us into the realm of application-layer protocols. An application-layer protocol defines how an application's processes, running on different end systems, pass messages to each other. In particular, an application-layer protocol defines:

What I said. It shouldn't be the final outcome that the true about Application. You look at this article for information on a person want to know is Application.

Application

o The types of messages exchanged, for example, request messages and response messages
o The syntax of the assorted message types, such as the fields in the message and how the fields are delineated
o The semantics of the fields, that is, the meaning of the information in the fields
o Rules for determining when and how a process sends messages and responds to messages

Some application-layer protocols are specified in Rfcs and are therefore in the group domain. For example, the Web's application-layer protocol, Http (the Hyper Text transfer Protocol (Rfc 2616]), is ready as an Rec. If a browser developer follows the rules of the Http Rfc, the browser will be able to retrieve Web pages from any Web server that has also followed the rules of the Http Rfc.

Many other application-layer protocols are proprietary and intentionally not ready in the group domain. For example, many existing P2P file-sharing systems use proprietary application-layer protocols.

It is foremost to distinguish in the middle of network applications and application- layer protocols. An application-layer protocol is only one piece of a network application. Let's look at a consolidate of examples. The Web is a client-server application that allows users to gain documents from Web servers on demand. The Web application consists of many components, including a appropriate for document formats (that is, Html), Web browsers (for example, Firefox and Microsoft Internet Explorer), Web servers (for example, Apache and Microsoft servers), and an application-layer protocol. The Web's application-layer protocol, H'I' defines the format and sequence of the messages that are passed in the middle of browser and Web server. Thus, Http is only one piece (albeit, an foremost piece) of the Web application. As other example, an Internet e-mail application also has many components, including mail servers that house user mailboxes; mail readers that allow users to read and create messages; a appropriate for defining the buildings of an e-mail message; and application-layer protocols that define how messages are passed in the middle of servers, how messages are passed in the middle of servers and mail readers, and how the contents of definite parts of the mail message (for example, a mail message header) are to be interpreted. The valuable application-layer protocol for electronic mail is Smtp (Simple Mail transfer Protocol) [Rfc 2821]. Thus, e-mail's valuable application-layer protocol, Smtp, is only one piece (albeit, an foremost piece) of the e-mail application.

I hope you have new knowledge about Application. Where you can put to used in your day-to-day life. And just remember, your reaction is passed about Application.