Difference between connection oriented and connectionless protocol

Question :

Difference between connection oriented and connectionless protocol

With a connectionless protocol, clients connect to the server, make a request, get a response, and then disconnect. For the Internet, HTTP is a connectionless protocol. With a connection-oriented protocol, clients connect to the server, make a request, get a response, and then maintain the connection to handle future requests. An example of a connection-oriented protocol is File Transfer protocol (FTP). When we connect to an FTP server, the connection remains open after you download a file. The maintenance of this connection consumes system resources. A server with too many open connections quickly gets overloaded. Consequently, many FTP servers are configured to allow only 250 open connections at one time, so only 250 users can access the FTP server at once.

Connectionless protocols differ from connection-oriented protocols in the way requests and responses to requests are handled. HTTP is a connectionless protocol. When clients connect to the HTTP server being a connectionless protocol, they make a request are used after the transaction is finished. Consequently with low system overhead. The drawback to connectionless protocols is that when the same client requests more data, the Connection must be re-established. To web users, this means a delay whenever they request more information.