The example of protocol is important. I believe that with protocols you have a way to communicate with people. For example, a person should not eat a certain color of salad or drink a certain brand of beer, but you should still be able to communicate with them in order to avoid conflict.
The protocol goes beyond the protocol itself, as there will be people who will not follow it, and there will be people who will understand how it works.
There are two types of protocols. The first is connectionless, which is when you can communicate and not have any conversations with other people. These are the protocols that people use to connect with each other, such as when you send a message to someone via a phone call. The second type is connection-oriented, which is when you are able to communicate and have some conversations with other people. These are the protocols we use to communicate with each other on the Internet, like a chat room.
Connectionless protocols are the ones that we’re going to explore in this lesson. Connection-oriented protocols are a little more involved, and one of the best ways to explore how one of the protocols we’ll be exploring in this lesson relates to one of the best tools for connection-oriented communication, called the TCP/IP protocol.
The TCPIP protocol is a connection-oriented protocol. In other words, it’s designed to run across the Internet without a central server. This is a nice way to get familiar with the TCPIP protocol and how it works, but it’s also one of the best ways to get a feel for what Connection-Oriented protocols are like.
So one thing that TCPIP is very good at is connecting people together. The two of you (or the person connecting) can send each other bits of information or messages, which are then passed across the Internet. To do this, you need a central server, and with TCPIP you have one. So the two of you have to communicate with a central server.
However, it’s also very easy to send messages across the Internet and connect people with no central server at all. The server is a central “hub,” and as long as there are two of you on the Internet, the two of you can send information to each other. But you can’t send two messages to the same server at the same time, so you have to get them to separate them.
This is the connectionless protocol. This is the thing we talked about earlier. When I say connectionless, I mean it doesn’t matter if you have an internet connection or not. It’s the idea that you can send information to another server, but the two of you have to get to separate times before you can send the information to each other. Now this is all possible because we have a central server.
But our central server is something we can’t get to. Its also not something we have to constantly worry about. I mean, we can always send a message to it, but we can also not. So that means for the rest of us, we can’t send a message to the central server, because we have to get it to the other servers.
That means we aren’t connected to each other, which doesn’t really sound like much of a problem. But it does feel a little like we’re just stuck in a loop. It makes sense though because it’s like we aren’t really doing anything at all. Like, we’re just sitting there waiting, we’re just sitting there in this empty space.