 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| n |
Characteristics
|
|
|
– |
stateless,
client/server, request/response
|
|
|
– |
needs
a connection oriented protocol (TCP), one connection per
|
|
|
request
(some enhancements in HTTP 1.1)
|
|
|
– |
primitive
caching and security
|
|
| n |
Problems
|
|
|
– |
designed
for large bandwidth (compared to wireless access) and
|
|
|
low
delay
|
|
|
– |
big
and redundant protocol headers (readable for humans, stateless,
|
|
therefore
big headers in ASCII)
|
|
|
– |
uncompressed
content transfer
|
|
|
– |
using
TCP
|
|
|
n |
huge
overhead per request (3-way-handshake) compared with the
|
|
|
content,
e.g., of a GET request
|
|
|
n |
slow-start
problematic
|
|
|
– |
DNS
lookup by client causes additional traffic
|
|
