This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi Rahul, This is not given in the question. What I understand whether the connection persist between mulitple request between web server and client, or web server uses diffrent connection for each request via connectionless and connectionbase.
But not very sure as I am also confused with the question. Question is what is HTTP 1) Stateless 2) Stateful 3) Connectionless 4) Connectionbase
HTTP is stateless, so if only one answer is correct, then that's the one.
Connection can mean a number of different things, so without context it's hard to say what is meant here. Fundamentally, HTTP is based on TCP/IP, which is connection-less, like all store-and-forward network architectures. But HTTP operates on a higher level than TCP, and abstracts away all the intermediate store/forward steps, thereby creating the illusion of an actual connection (even more so with the keep-alive feature).
IP is not connection based but TCP (which sits on top of IP) is. And since HTTP is on top of TCP, HTTP is also connection based. By "connection" it means that the sender and receiver establish a handshake (as defined by TCP) and guarantee that the entire message gets received.
The correct answers are stateless and connection based.
HTTP is Stateless and Connectionbase protocol. I am sure that no body has doubt about its Statelessness.
Now as we say, we have various protocol stack. And 'connection-orientedness' or 'connectionless-ness' of layer n layer protocol is not really dependent on these properties of n-1 layer protocol. In other words you can build connection-oriented communication layer over connectionless layer (like some chatting application do over UDP protocol)or you can .... build connectionless communication layer over connection-oriented layer .... something which HTTP do!!! hence it is connectionbase protocol.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com