Answer Posted / rajani nagandla

Http operates on what is called a request-response
paradigm. This means that a _client_ generates a request
for information, and passes it to the server, which answers
it. In the original implementation of HTTP, each request
created a new socket connection to the server, sent the
request, then read from that connection to get the response.

This approach had one big advantage - it was simple. Simple
to describe, simple to understand, and simple to code. It
also had one big disadvantage - it was slow. So, keep-alive
connections were invented for HTTP.

HTTP/1.0
Under HTTP 1.0, there is no official specification for how
keepalive operates. It was, in essence, tacked on to an
existing protocol. If the browser supports keep-alive, it
adds an additional header to the request:

Connection: Keep-Alive

Then, when the server receives this request and generates a
response, it also adds a header to the response:

Connection: Keep-Alive

Following this, the connection is NOT dropped, but is
instead kept open. When the client sends another request,
it uses the same connection. This will continue until
either the client or the server decides that the
conversation is over, and one of them drops the connection.

HTTP/1.1
Under HTTP 1.1, the official keepalive method is different.
All connections are kept alive, unless stated otherwise
with the following header:

Connection: close

The Connection: Keep-Alive header no longer has any meaning
because of this.

Additionally, an optional Keep-Alive: header is described,
but is so underspecified as to be meaningless. Avoid it.

What is network programming in java?

938

---

What is socket in java?

1009

---

Explain a time server?

988

---

What is HttpURL connection ?

982

---

What is cookies in networking ?

966

---

Public serversocket(int port, int queuelength) throws ioexception, bindexception?

1051

---

Explain look for local ports?

1054

---

What is an http server?

947

---

What is network interface name?

894

---

Tell me about networking classes and interfaces.

1001

---

How we can make simple java program for Server/Client Communication

1026

---

What is an http redirector?

926

---

What is the Difference between socket and servlet?

1220

---

If you do not want your program to halt while it waits for a connection, put the call to accept( ) in a separate thread?

914

---

Why socketutil is used?

974

---