|
|
|
|
|
by jraph
2238 days ago
|
|
Someone would have ended up inventing some X-Session-Id HTTP header that the server would send to the user agent, and the user-agents supporting the "HTTP Sessions extension" would send back a X-Session-Id with the same content to the same origin. A special empty value would have been used to terminate the session, from the client or from the server. Another HTTP header, X-Session-Expiration, would have been added to expire sessions. /s |
|
I imagine the page would need to also use some sort of dictionary-based compression for efficient transfer of the page if it has many links on it. ;-)
On the plus side, you wouldn’t need megabytes of cookies...