Why do Ember.js authentication solutions use a token instead of server sessions?

Question

Every auth system I saw for Ember was based on tokens. Is there a good reason why this is done instead of relying on server-side sessions? Given that ajax is just plain HTTP requests, I don't see any flaws in server-side sessions to maintain authentication status.

Answer 1

Ember.js uses REST to communicate with the server. REST requires the server to be stateless. Token authentication does not require the server to have status, while server-side sessions.

EDIT: here you will find a detailed answer on using sessions with REST: fooobar.com/questions/13076 / ...

Answer 2

Here is an example of another authentication method.