3 ms·
It doesn't seem like the proposals are "fully" compatible with HTTP. Some of them are entirely different encodings. And I doubt people are thinking of carrying
by MichaelGG 14y ago
It doesn't seem like the proposals are "fully" compatible with HTTP. Some of them are entirely different encodings. And I doubt people are thinking of carrying over comments in headers and line folding...
What actually is the proposal to eliminate cookies? Just provide some fixed "identifier" type field?
- comex 14y ago> And I doubt people are thinking of carrying over comments in headers and line folding... Heh, I don't think any reasonable web apps actually depend on the value of those :) > What actually is the proposal to eliminate cookies? Just provide some fixed "identifier" type field? Unfortunately, I don't think there is a concrete proposal to compare to, other than Given how almost universal the "session" concept on the Internet we should add it to the HTTP/2.0 standard, and make it available for HTTP routers to use as a "flow-label" for routing.
- pfraze 14y agoI'd say the cookies situation could be solved by one-page apps. Because the software persists across page-views, it'll be able to maintain session using some other mechanism (localstorage, the lifetime of the tab, whatever). The user could then disable cookies and not be worried about tracking.
- stephenr 14y agoso your "solution" for cookies, is to mandate that all web apps must use ajax, and pass session IDs as part of the URL for all requests?