|
Grid Application Toolkit A simple API for Grid Applications |
|
- Home
- API-Specification
- API-Overview
- Status
- Reference
- Manual
- Download
- Java-Reference
- GridLab - WP-1
- Links
C
Java
General
Next: HTTPS Up: HTTP Previous: Server Response Contents Closing a ConnectionThe connection can be closed by either the client or server. In contrast to the earlier HTTP/1.0 protocol, in the HTTP/1.1 protocol a connection between a server and a client can be reused and does not have to be closed after every request/response pair is issued. As in the physical world, so in the world of bits; recycling is a GoodIdea. In the physical world it keeps us from running out of resources, and it serves the same purpose in bit-world. For example, if we were to fire a mass of miniscule missives down the ``wire'' to our suited, then the majority of our network resources would be frittered on closing and opening, closing and opening, closing and opening...connections; such primitive, knuckle-dragging behavior really should be illegal. A more evolved tack involves walking upright, using tools, then reusing these tools. (Tens-of-thousands of years of evolution and we still haven't really taken this lesson to heart.) The connection should not be closed after each request/response. It should be kept open so multitudes of request/response pairs can be sent down this same ``wire.'' This is now possible in HTTP/1.1 the evolution of HTTP/1.0.
Next: HTTPS Up: HTTP Previous: Server Response Contents Andre Merzky 2004-05-13 |