About HTTP and TCP/IP

TCP/IP is a family of communication protocols used to connect computer systems in a network, and is named after two of the protocols in the family: Transmission Control Protocol (TCP) and Internet Protocol (IP). Hypertext Transfer Protocol (HTTP) is a member of the TCP/IP family.

HTTP only defines what the browser and web server say to each other, not how they communicate. The actual work of moving bits and bytes back and forth across the network is done by TCP and IP.

tcp is a communications protocol, transmission control protocol I think, which operates the transport layer and allows the packets of information to make it around the internet from the host to the receiving computer. when paired with the ip protocol, tcp/ip, this is what makes up the backbone of the internet.

http is an access protocol that can use the internet to access the web or web pages. It is a method that the browser software uses to access a particular file or web page on the internet. the web, or web pages and http are technically not the internet, just one of the many types of protocols that can be used to share information on the internet. Another example of one of these access protocols would be ftp.

ftp for file transfer

What if the communication can be remembered? how will this make a change in the current web development? as now it's a stateless protocol TCP/IP. Then we don't need any state management techniques in ASP.NET if TCP/IP can remember the communication happening b/w client and server.

ASP.NET is an http request processing technology so as other web devolopment platforms like Ruby On Rails

SOAP Protocol
-----------------
It relies on Extensible Markup Language (XML) for its message format, and usually relies on other Application Layer protocols, most notably Hypertext Transfer Protocol (HTTP) and Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission. SOAP can be used over any transport protocol such as HTTP, SMTP or even TCP).