Hi All, I am really confused to decide weather HTTP is a Connection oriented(I though may be this is based on TCP ,which is connection oriented) or is just connection less can any once clarify this please.
It's connectionless because requires a new connection for each request. That is, it doesn't maintain a single connection for the whole communication between client and server. [ June 08, 2004: Message edited by: Jose Botella ]
This is interesting and confusing for a couple reasons.
For one, we often talk about web server sessions. The server maintains some state and remembers the user and what they're doing and that sounds a lot like the definition of a connection. The distinction is that web servers build their session stuff on top of the HTTP protocol, and session is not part of the HTTP protocol. You can have HTTP servers with no sessions.
Another confusing bit is that IP is connection oriented. HTTP makes an IP connection for the duration of one HTTP request-response and then breaks it. If you read up on HTTP there is a three part handshake - three IP messages - to one request. I'm foggy on this but it's something like Client: I'd like to send you a message Server: Ok, send me a message Client: Here's the message.
I think it's cool that we run connection oriented web sites over connectionless HTTP over connection-oriented IP over connectionless TCP. Protocol stacks can be fun.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Joined: Jun 08, 2004
Thanks guys ...Now i am clarified
Joined: Jul 03, 2001
IP is connectionless and TCP is connection oriented.
Joined: Jan 29, 2003
Thanks, Jose. I passed my networking class, but instantly forgot most of it.
Based on the OSI 7-layers model, HTTP is an application layer protocol. (layer 7). It uses IP and TCP (layer 3 and layer 4) protocols as its transport. It does NOT support UDP.
Since HTTP uses TCP, it is therefore connection-oriented.
However, what confuses most people is that each web page requests opens multiple HTTP connections to the web server. For instance, if a web page has 5 images, the web browser will likely open 5 different HTTP connections to the web server. After each image is delivered, the connections are closed one-by-one.
This is based on the request-response nature of HTTP. Even though HTTP connections are opened and closed rapidly, the HTTP protocol is connection-oriented since it uses TCP.