Thomas Kunz
Systems and Computer Engineering
15
HTTP 1.0 and Mobility
nCharacteristics
–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
nProblems
–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
nhuge overhead per request (3-way-handshake) compared
with the content, e.g., of a GET
request
nslow-start problematic
–DNS lookup
by client causes additional traffic