Hacker News new | past | comments | ask | show | jobs | submit login

> Fielding also felt that cookies are not RESTful because they add state to what should be a stateless system, but their usage was already entrenched.2

I'd be curious to see a web without cookies.

I understand the desire for stateless, but given how many things need logins and an user "session" how would that work without cookies?




>I understand the desire for stateless, but given how many things need logins and an user "session" how would that work without cookies?

RESTful is ok for public APIs. If you design both the client and server, you don't need to be stateless.


> If you design both the client and server, you don't need to be stateless.

And you also don't need to be RESTful.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: