 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| n |
Push
technology
|
|
|
|
– |
real
pushing, not a client pull needed, channels etc.
|
|
|
| n |
HTTP/1.1
|
|
|
|
– |
client/server
use the same connection for several request/response
|
|
|
transactions
|
|
|
|
– |
multiple
requests at beginning of session, several responses in same order
|
|
|
|
– |
enhanced
caching of responses (useful if equivalent responses!)
|
|
|
|
– |
semantic
transparency not always achievable: disconnected, performance,
|
|
availability
-> most up-to-date version...
|
|
|
|
– |
several
more tags and options for controlling caching (public/private,
|
|
|
max-age,
no-cache etc.)
|
|
|
|
– |
relaxing
of transparency on app. request or with warning to user
|
|
|
|
– |
encoding/compression
mechanism, integrity check, security of proxies,
|
|
|
authentication,
authorization...
|
|
|
| n |
Cookies:
well..., stateful sessions, not really integrated...
|
|
